Methods and apparatus for coordinated utilization of quasi-licensed wireless spectrum

ABSTRACT

Methods and apparatus for providing quasi-licensed spectrum access within a prescribed area or venue, including to users or subscribers of one or more Mobile Network Operators (MNOs). In one embodiment, the quasi-licensed spectrum utilizes 3.5 GHz CBRS (Citizens Broadband Radio Service) spectrum allocated by a Federal or commercial SAS (Spectrum Access System) to a managed content delivery network that includes one or more wireless access nodes (e.g., CBSDs) in data communication with a controller, and the core(s) of the MNO network(s). In one variant, the controller dynamically allocates (i) spectrum within the area or venue within CBRS bands, and (ii) MNO “roaming” users or subscribers to CBRS bands (e.g., via extant LTE-TD technology). In one particular implementation, the managed network comprises a Multiple Systems Operator (MSO) network such as a cable or satellite network, and the MSO and MNO coordinate to implement user-specific and/or data-specific policies for the roaming MNO subscribers.

RELATED APPLICATIONS

This application is related to co-owned and copending U.S. patentapplication Ser. No. 15/677,940 filed Aug. 15, 2017 and entitled“METHODS AND APPARATUS FOR DYNAMIC CONTROL AND UTILIZATION OFQUASI-LICENSED WIRELESS SPECTRUM”, incorporated herein by reference inits entirety.

COPYRIGHT

A portion of the disclosure of this patent document contains materialthat is subject to copyright protection. The copyright owner has noobjection to the facsimile reproduction by anyone of the patent documentor the patent disclosure, as it appears in the Patent and TrademarkOffice patent files or records, but otherwise reserves all copyrightrights whatsoever.

BACKGROUND 1. Technological Field

The present disclosure relates generally to the field of wirelessnetworks and specifically, in one or more exemplary embodiments, tomethods and apparatus for dynamically controlling and optimizingutilization of quasi-licensed radio frequency spectrum, such as forexample those providing connectivity via Citizens Broadband RadioService (CBRS) technologies.

2. Description of Related Technology

A multitude of wireless networking technologies, also known as RadioAccess Technologies (“RATs”), provide the underlying means of connectionfor radio-based communication networks to user devices. Such RATs oftenutilize licensed radio frequency spectrum (i.e., that allocated by theFCC per the Table of Frequency Allocations as codified at Section 2.106of the Commission's Rules. In the United States, regulatoryresponsibility for the radio spectrum is divided between the U.S.Federal Communications Commission (FCC) and the NationalTelecommunications and Information Administration (NTIA). The FCC, whichis an independent regulatory agency, administers spectrum fornon-Federal use (i.e., state, local government, commercial, privateinternal business, and personal use) and the NTIA, which is an operatingunit of the Department of Commerce, administers spectrum for Federal use(e.g., use by the Army, the FAA, and the FBI). Currently only frequencybands between 9 kHz and 275 GHz have been allocated (i.e., designatedfor use by one or more terrestrial or space radio communication servicesor the radio astronomy service under specified conditions). For example,a typical cellular service provider might utilize spectrum for so-called“3G” (third generation) and “4G” (fourth generation) wirelesscommunications as shown in Table 1 below:

TABLE 1 Technology Bands 3G 850 MHz Cellular, Band 5 (GSM/GPRS/EDGE).1900 MHz PCS, Band 2 (GSM/GPRS/EDGE). 850 MHz Cellular, Band 5(UMTS/HSPA+ up to 21 Mbit/s). 1900 MHz PCS, Band 2 (UMTS/HSPA+ up to 21Mbit/s). 4G 700 MHz Lower B/C, Band 12/17 (LTE). 850 MHz Cellular, Band5 (LTE). 1700/2100 MHz AWS, Band 4 (LTE). 1900 MHz PCS, Band 2 (LTE).2300 MHz WCS, Band 30 (LTE).

Alternatively, unlicensed spectrum may be utilized, such as that withinthe so-called ISM-bands. The ISM bands are defined by the ITU RadioRegulations (Article 5) in footnotes 5.138, 5.150, and 5.280 of theRadio Regulations. In the United States, uses of the ISM bands aregoverned by Part 18 of the Federal Communications Commission (FCC)rules, while Part 15 contains the rules for unlicensed communicationdevices, even those that share ISM frequencies. Table 2 below showstypical ISM frequency allocations:

TABLE 2 Frequency Center Avail- range Type frequency ability Licensedusers 6.765 MHz- A  6.78 MHz Subject to Fixed service & mobile 6.795 MHzlocal ac- service ceptance 13.553 MHz- B  13.56 MHz World- Fixed &mobile services 13.567 MHz wide except aeronautical mobile (R) service26.957 MHz- B  27.12 MHz World- Fixed & mobile service 27.283 MHz wideexcept aeronautical mobile service, CB radio 40.66 MHz- B  40.68 MHzWorld- Fixed, mobile services & 40.7 MHz wide earthexploration-satellite service 433.05 MHz- A 433.92 MHz only in amateurservice & 434.79 MHz Region 1, radiolocation service, subject toadditional apply the local ac- provisions of footnote ceptance 5.280 902MHz- B   915 MHz Region 2 Fixed, mobile except 928 MHz only (withaeronautical mobile & some ex- radiolocation service; in ceptions)Region 2 additional amateur service 2.4 GHz- B  2.45 GHz World- Fixed,mobile, 2.5 GHz wide radiolocation, amateur & amateur-satellite service5.725 GHz- B   5.8 GHz World- Fixed-satellite, 5.875 GHz wideradiolocation, mobile, amateur & amateur- satellite service 24 GHz- B24.125 GHz World- Amateur, amateur- 24.25 GHz wide satellite,radiolocation & earth exploration-satellite service (active) 61 GHz- A 61.25 GHz Subject to Fixed, inter-satellite, 61.5 GHz local ac- mobile& radiolocation ceptance service 122 GHz- A  122.5 GHz Subject to Earthexploration-satellite 123 GHz local ac- (passive), fixed, inter-ceptance satellite, mobile, space research (passive) & amateur service244 GHz- A   245 GHz Subject to Radiolocation, radio 246 GHz local ac-astronomy, amateur & ceptance amateur-satellite service

ISM bands are also been shared with (non-ISM) license-freecommunications applications such as wireless sensor networks in the 915MHz and 2.450 GHz bands, as well as wireless LANs and cordless phones inthe 915 MHz, 2.450 GHz, and 5.800 GHz bands.

Additionally, the 5 GHz band has been allocated for use by, e.g., WLANequipment, as shown in Table 3:

TABLE 3 Dynamic Freq. Selection Band Name Frequency Band Required (DFS)?UNII-1 5.15 to 5.25 GHz No UNII-2 5.25 to 5.35 GHz Yes UNII-2 Extended 5.47 to 5.725 GHz Yes UNII-3 5.725 to 5.825 GHz No

User client devices (e.g., smartphone, tablet, phablet, laptop,smartwatch, or other wireless-enabled devices, mobile or otherwise)generally support multiple RATs that enable the devices to connect toone another, or to networks (e.g., the Internet, intranets, orextranets), often including RATs associated with both licensed andunlicensed spectrum. In particular, wireless access to other networks byclient devices is made possible by wireless technologies that utilizenetworked hardware, such as a wireless access point (“WAP” or “AP”),small cells, femtocells, or cellular towers, serviced by a backend orbackhaul portion of service provider network (e.g., a cable network). Auser may generally access the network at a “hotspot,” a physicallocation at which the user may obtain access by connecting to modems,routers, APs, etc. that are within wireless range.

CBRS—

In 2016, the FCC made available Citizens Broadband Radio Service (CBRS)spectrum in the 3550-3700 MHz (3.5 GHz) band, making 150 MHz of spectrumavailable for mobile broadband and other commercial users. The CBRS isunique, in that it makes available a comparatively large amount ofspectrum (frequency bandwidth) without the need for expensive auctions,and without ties to a particular operator or service provider.

Moreover, the CBRS spectrum is suitable for shared use betweengovernment and commercial interests, based on a system of existing“incumbents,” including the Department of Defense (DoD) and fixedsatellite services. Specifically, a three-tiered access framework forthe 3.5 GHz is used; i.e., (i) an Incumbent Access tier 102, (ii)Priority Access tier 104, and (iii) General Authorized Access tier 106.See FIG. 1. The three tiers are coordinated through one or more dynamicFederal Spectrum Access Systems (FSAS) 202 as shown in FIG. 2.

Incumbent Access (existing DOD and satellite) users 102 includeauthorized federal and grandfathered Fixed Satellite Service (FSS) userscurrently operating in the 3.5 GHz band shown in FIG. 1. These userswill be protected from harmful interference from Priority Access License(PAL) and General Authorized Access (GAA) users. The sensor networks,operated by Environmental Sensing Capability (ESC) operators, make surethat incumbents and others utilizing the spectrum are protected frominterference.

The Priority Access tier 104 (including acquisition of spectrum for upto three years through an auction process) consists of Priority AccessLicenses (PALs) that will be assigned using competitive bidding withinthe 3550-3650 MHz portion of the band. Each PAL is defined as anon-renewable authorization to use a 10 MHz channel in a single censustract for three years. Up to seven (7) total PALs may be assigned in anygiven census tract, with up to four PALs going to any single applicant.Applicants may acquire up to two-consecutive PAL terms in any givenlicense area during the first auction.

The General Authorized Access tier 106 (for any user with an authorized3.5 GHz device) is licensed-by-rule to permit open, flexible access tothe band for the widest possible group of potential users. GeneralAuthorized Access users are permitted to use any portion of the3550-3700 MHz band not assigned to a higher tier user and may alsooperate opportunistically on unused Priority Access channels. See FIG. 2a.

The FCC's three-tiered spectrum sharing architecture of FIG. 1 utilizes“fast-track” band (3550-3700 MHz) identified by PCAST and NTIA, whileTier 2 and 3 are regulated under a new Citizens Broadband Radio Service(CBRS). CBSDs (Citizens Broadband radio Service Devices—in effect,wireless access points) 206 (FIG. 2) can only operate under authority ofa centralized Spectrum Access System (SAS) 202. Rules are optimized forsmall-cell use, but also accommodate point-to-point andpoint-to-multipoint, especially in rural areas.

Under the FCC system, the standard FSAS 202 includes the followingelements: (1) CBSD registration; (2) interference analysis; (3)incumbent protection; (4) PAL license validation; (5) CBSD channelassignment; (6) CBSD power limits; (7) PAL protection; and (8)FSAS-to-FSAS coordination. As shown in FIG. 2, these functions areprovided for by, inter alia, an incumbent detection (i.e., environmentalsensing) function 207 configured to detect use by incumbents, and anincumbent information function 209 configured to inform the incumbentwhen use by another user occurs. An FCC database 211 is also provided,such as for PAL license validation, CBSD registration, and otherfunctions.

An optional Domain Proxy (DP) 208 is also provided for in the FCCarchitecture. Each DP 208 includes: (1) SAS interface GW includingsecurity; (2) directive translation between CBSD 206 and domaincommands; (3) bulk CBSD directive processing; and (4) interferencecontribution reporting to the FSAS.

A domain is defined is any collection of CBSDs 206 that need to begrouped for management; e.g.: large enterprises, venues, stadiums, trainstations. Domains can be even larger/broader in scope, such as forexample a terrestrial operator network. Moreover, domains may or may notuse private addressing. A Domain Proxy (DP) 208 can aggregate controlinformation flows to Commercial SAS (CSAS), not shown, and generateperformance reports, channel requests, heartbeats, etc.

CBSDs 206 can generally be categorized as either Category A or CategoryB. Category A CBSDs have an EIRP or Equivalent Isotropic Radiated Powerof 30 dBm (1 Watt)/10 MHz, fixed indoor or outdoor location (with anantenna <6 m in length if outdoor). Category B CBSDs have 47 dBm EIRP(50 Watts)/10 MHz, and fixed outdoor location only. Professionalinstallation of Category B CBSDs is required, and the antenna must beless than 6 m in length. All CBSD's have a vertical positioning accuracyrequirement of +/−3 m. Terminals (i.e., user devices akin to UE) have 23dBm EIRP (0.2 Watts)/10 MHz requirements, and mobility of the terminalsis allowed.

In terms of spectral access, CBRS utilizes a time division duplex (TDD)multiple access architecture.

Unlicensed Spectrum Technologies—

Extant wireless technologies intended for use in the unlicensed spectrum(such as Wi-Fi and LTE-U and LTE-LAA) must coexist with other users inthose bands, and hence necessarily employ contention managementtechniques to help optimize performance. For example, Wi-Fi utilizes aback-off mechanism for collision avoidance known as carrier-sensemultiple access with collision avoidance (“CSMA/CA”). In particular,when a first network node or station receives a packet to be sent toanother node or station, Wi-Fi (according to, e.g., the prevailing802.11 standard under which the system operates) initiates physicalcarrier sensing and virtual carrier sensing mechanisms to determinewhether the medium (e.g., a channel and/or frequency used by the Wi-Fitransceiver) is busy or occupied by other transmissions (physical andvirtual carrier sensing). In addition to the conditions set by physicalcarrier sensing and virtual carrier sensing, the Wi-Fi CSMA/CA mayimpose further checks by a node to ensure that the channel on which thepacket is to be sent is clear.

Likewise, LTE-U collision avoidance mechanisms (at least in theory)attempt to choose a free or idle channel (i.e., not in use) in which noother LTE-U node or Wi-Fi AP is operating; if a free channel is notfound, the LTE-U node should apply duty cycle procedures that allow thenode to share a channel with Wi-Fi and other LTE-U signals. In somecircumstances, duty cycling parameters may be adapted to usage of othersignals, e.g., in response to Wi-Fi usage.

However, even with such mechanisms, increasing numbers of users (whetherusers of wireless interfaces of the aforementioned standards, or others)invariably lead to “crowding” of the spectrum, including interference.Interference may also exist from non-user sources such as solarradiation, electrical equipment, military uses, etc. In effect, a givenamount of spectrum has physical limitations on the amount of bandwidthit can provide, and as more users are added in parallel, each userpotentially experiences more interference and degradation ofperformance. Simply stated, contention management has limits on thebenefits it can provide.

Moreover, technologies such as Wi-Fi have limited range (due in part tothe unlicensed spectral power mask imposed in those bands), and maysuffer from spatial propagation variations (especially inside structuressuch as buildings) and deployment density issues. Wi-Fi has become soubiquitous that, especially in high-density scenarios such ashospitality units (e.g., hotels), enterprises, crowded venues, and thelike, the contention issues may be unmanageable, even with a plethora ofWi-Fi APs installed to compensate. Yet further, there is generally nocoordination between such APs, each in effect contending for bandwidthon its backhaul with others.

Additionally, lack of integration with other services provided by e.g.,a managed network operator, typically exists with unlicensed technologysuch as Wi-Fi. Wi-Fi typically acts as a “data pipe” opaquely carried bythe network operator/service provider.

Licensed Spectrum Operators—

A variety of different types of mobile network (e.g., cellular)operators exist, as described below:

1) Mobile Network Operator (MNO): The MNO is responsible for thecreation, operation, and maintenance of the mobile networkinfrastructure. MNOs will typically purchase/lease their licensedspectrum from the regulatory body of the relevant territory, and alsopurchase/lease the network infrastructure and equipment from a pluralityof equipment vendors and network integrators. Additionally, MNOs mustselect and obtain suitable handsets for their subscribers, which arecompatible with the installed infrastructure for all intended uses(e.g., voice and data). The MNO also typically maintains its ownBusiness and Operational Support System (BOSS), and are responsible forbilling MNO subscribers, tracking data such as used minutes, roamingcharges, etc.

2) Mobile Virtual Network Operator (MVNO): An MVNO typically utilizesthe infrastructure maintained and provided by the MNO (e.g.,“piggy-backs” on the existing MNO capabilities) to provide service to adifferent set of subscribers not served by the MNO. For example, an MNOmay have unused capacity that it may be willing to lease or sell to theMVNO at a different rate than that associated with its (primary)subscribers. MVNOs will often have their own BOSS capability, includingfor billing its own customers; however, some MVNOs rely on the MNOsupport and BOSS capabilities to provide data, such as e.g., usageinformation for the MVNO customers, such that the MVNO can accuratelybill them. In yet another model, the MNO BOSS capabilities may assumeall billing responsibilities for the MVNO(s).

3) Mobile Virtual Network Aggregator (MVNA): To enhance economies ofscale, an MVNA may be used to combine or aggregate two or more smallerMVNOs for obtaining service to the MNO. In this role, the MVNA acts asan interface between the individual smaller MVNOs and the MNO.Accordingly, an MVNA will typically not have its own direct subscribers,but rather only service the MVNOs that it represents/aggregates. Itwould typically also have its own BOSS to be able to generate andprovide billing and related data for the individual constituent MVNOs.

Closely relates to the MVNA is the Mobile Virtual Network Enabler(MVNE), which in effect enables “outsourcing” of all functionalityrelated to virtual mobile networks. The MVNE can typically provideservices to such as billing, network element provisioning, operations,BOSS functions, etc. to small MVNOs, and does not have any end-usercustomers of its own. Rather, the MVNE provides a “back end” for thefront-facing (i.e., subscriber-facing) MVNO(s).

Notably, under any of the foregoing models, MNO/MVNO subscribers areprovided cellular service only by these networks/entities. Specifically,depending on the particular air interface technology selected (e.g.,3GPP/LTE/LTE-A, WCDMA, or GSM), the subscriber has two options forconnection for voice or data services: (i) cellular based technology, or(ii) WLAN (e.g., Wi-Fi). LTE coverage in licensed spectrum cellularnetworks is widely available, but there is significant burden on datarates and throughput. Specifically, while coverage over broadgeographical areas may exist, MNO networks are becoming increasinglycongested with many users and “data hungry” applications such as videostreaming. Adding additional capacity in such MNO networks is hugelyexpensive, and average revenue per user (ARPU) on MNO networks issteadily declining over time.

Further, while both of these options may be available in some areas orvenues, one or both may not be available in others, or may operate inless-than-optimal fashion. For example, WLAN coverage via unlicensedspectrum can be spotty and contentious (depending on the presence ofinterference, competing users, etc. as previously described), andcellular coverage, even when available, typically costs the user in onefashion or another (whether for minutes or GB of data used, roamingcharges, or even increased batter consumption due to having tocommunicate with the potentially distance eNodeB or other cell site).Similarly, LTE data performance may vary as a function of the coveragearea, such that user experience for e.g., the aforementioned data-hungryapplications is not optimized over that interface.

Moreover, some of the benefits of cellular service are lost whentransitioning to WLAN (where available), including benefits orpriorities for service afforded by the subscriber's MNO as part of theirplan. WLAN use is typically “take it as you find it,” including anyservice or other limitations associated therewith.

Extant CBRS architectures, while promising from the standpoint ofreduced contention for spectrum, currently lack such network-widecoordination and integration, as well as implementation details enablingoptimization of user experience, especially for users of a multi-modecontent distribution network such as that of a cable, satellite, orterrestrial service operator.

Moreover, such extant CBRS architectures do not account for integrationwith MNOs (e.g., cell service networks), such that the user experiencewhen using and/or transition to/from CBRS (i.e., to/from licensedspectrum cell service) is seamless.

SUMMARY

The present disclosure addresses the foregoing needs by providing, interalia, methods and apparatus for dynamically controlling access to andutilization of quasi-licensed spectrum (such as for example that ofCBRS) in conjunction with one or more MNOs and users/subscribersthereof.

In one aspect, a method for providing wireless service within a firstwireless network infrastructure to a mobile user device served by asecond wireless network infrastructure is disclosed. In one embodiment,the method includes: at least temporarily registering the mobile userdevice with the first wireless network infrastructure; selecting atleast one quasi-licensed band for use by the mobile user device withinthe first wireless network infrastructure; communicating data to themobile user device enabling the mobile user device to access theselected at least one quasi-licensed band for use; and establishingcommunication with the mobile user device using the at least onequasi-licensed band via one or more access points of the first wirelessnetwork infrastructure.

In one variant, the communicating data includes transmitting the data tothe mobile user device via a data interface between the first wirelessnetwork infrastructure and the second wireless network infrastructure.

In another variant, the method further includes communicating user datato and from the mobile user device via a data interface between thefirst wireless network infrastructure and the second wireless networkinfrastructure, the user data generated as part of a communicationsession established using the at least one quasi-licensed band and theone or more access points.

In yet another variant, the establishing communication with the mobileuser device using the at least one quasi-licensed band via one or moreaccess points of the first wireless network infrastructure includesusing an Long Term Evolution-Time Division Duplex (LTE-TDD) protocol toestablish communication within a Citizens Broadband Radio Service (CBRS)quasi-licensed band via at least one CBSD.

In a further variant, the establishing communication with the mobileuser device using the at least one quasi-licensed band via one or moreaccess points of the first wireless network infrastructure includesimposing at least one service policy associated with the second wirelessnetwork infrastructure as part of the communication. In oneimplementation thereof, the method further includes communicating userdata to and from the mobile user device via a data interface between thefirst wireless network infrastructure and the second wireless networkinfrastructure, the user data generated as part of a communicationsession established using the at least one quasi-licensed band and theone or more access points. The imposition of at least one service policyassociated with the second wireless network infrastructure as part ofthe communication includes imposing a QoS (quality of service policy)for at least a portion of the user data.

In still another variant, the method further includes communicating userdata to and from the mobile user device via a data interface between thefirst wireless network infrastructure and the second wireless networkinfrastructure, the user data generated as part of a communicationsession established using the at least one quasi-licensed band and theone or more access points. In one implementation, the communicating theuser data includes prioritizing the user data with respect to other userdata transacted by the one or more access points.

In another variant, the method further includes, prior to the selectingat least one quasi-licensed band for use by the mobile user devicewithin the first wireless network infrastructure: transmitting aspectrum request to a spectrum allocation authority; and receiving aspectrum grant from the allocation authority for at least a period oftime, the spectrum grant including the at least one quasi-licensed band.

In a further variant, the at least temporarily registering the mobileuser device with the first wireless network infrastructure includesobtaining data specific to the mobile user device form an authenticationentity of the second network infrastructure.

In another aspect of the disclosure, a method for providing mobilevisiting access services for at least one mobile client device isprovided. In one embodiment, the device is configured to use first andsecond wireless protocols, and the method includes: registering, whilethe at least one mobile client device is utilizing the first wirelessprotocol, the at least one mobile client device with a temporary serviceprovider network, the temporary service provider network comprising botha radio access network (RAN) and a core portion; allocatingquasi-licensed spectrum to the at least one mobile client device for usewithin the RAN; and causing the at least one mobile client device totransition from the first wireless protocol to the second wirelessprotocol.

In one variant, the first wireless protocol includes a Long TermEvolution (LTE)-FDD (frequency division duplex) cellular protocol, andthe second protocol includes an LTE-TDD (time division duplex) protocol.The LTE-FDD protocol is configured to use a cellular (licensed) band,while the second protocol is configured to use a CBRS band between 3.550and 3.700 GHz.

In a further variant, the allocating quasi-licensed spectrum includes:transmitting data to a domain proxy (DP), the DP configured tocommunicate at least a portion of the data to a Spectrum Access System(SAS) to obtain access to a Citizens Broadband Radio Service (CBRS)band; receiving from the DP data indicating a CBRS band allocation; andallocating at least a portion of the CBRS band allocation for use by atleast one mobile client device in communicating with an access point ofthe RAN.

In another variant, the registering the at least one mobile clientdevice with a temporary service provider network includes: receiving,from a cellular service provider network core portion, data indicativeof the at least one mobile device; and utilizing the received data toauthenticate the at least one mobile device within the temporary serviceprovider network pursuant to a service request issued from the at leastone mobile client device. In one implementation, the method also furtherincludes establishing data communication between the at least one mobileuser device and the cellular service provider network; and transactingone or more messages between a user device of the cellular serviceprovider network and the at least one mobile user device via thecellular service provider network and the temporary service providernetwork.

The transacting one or more messages between a user device of thecellular service provider network and the at least one mobile userdevice via the cellular service provider network and the temporaryservice provider network includes in another implementation utilizingboth a core portion of the cellular service provider network and a coreportion of the temporary service provider network.

In a further variant, the registering the at least one mobile clientdevice with a temporary service provider network includes: receiving, atthe temporary service provider network, a service request issued fromthe at least one mobile client device, the service request comprisingdata identifying the at least one mobile client device; transmitting thecomprising data identifying the at least one mobile client device to anauthentication entity of a cellular service provider; and receiving dataauthenticating the at least one mobile client device.

In another aspect of the disclosure, a method is disclosed whereby oneor more MNOs can use the MVNO/MSO core network to access Internetservices, thereby reducing round-trip delay for obtaining such servicesfor MNO subscribers, and improving the QoS provided.

In another aspect of the disclosure, network apparatus for use within afirst network is disclosed. In one embodiment, the network apparatus isconfigured to at least temporarily provide wireless service within aquasi-licensed frequency band to subscribers of a second network, andincludes: digital processor apparatus; network interface apparatus indata communication with the digital processor apparatus and configuredto transact data with one or more computerized entities of the secondnetwork; and a storage apparatus in data communication with the digitalprocessor apparatus and comprising at least one computer program.

In one variant, the at least one computer program is configured to, whenexecuted on the digital processor apparatus: receive first data from theone or more computerized entities relating to a subscriber deviceoperative within the second network; receive second data pursuant to arequest for wireless service from the subscriber device; based at leaston the received first and second data, authenticate the subscriberdevice; allocate quasi-licensed spectrum for use by at least thesubscriber device; cause transmission of first data to the one or morecomputerized entities of the second network, the first data enabling thesubscriber device to utilize the allocated quasi-licensed spectrum.

In one implementation, the at least one computer program is furtherconfigured to enable transaction of user data over at least a coreportion of the first network and a core portion of the second networkand via a data interface between the first and second networks. Forexample, the transaction of user data over at least a core portion ofthe first and second networks is configured to be conducted according toat least one user-specific or device-specific policy specified by thesecond network.

In one aspect of the disclosure, a method for providing wirelessconnectivity for at least one mobile client device is described. In oneembodiment, the method includes . . . .

In another aspect, methods for roaming MNO user access to CBRS servicesvia a managed content distribution network are disclosed. In oneembodiment, the methods include evaluating user network access requests,identifying MNO roaming user request therefrom, and allocating available(e.g., SAS-allocated) resources within a quasi-licensed band at leasttemporarily for the MNO users within the MSO quasi-licensed coveragearea, including data backhaul to the MNO core.

In an additional aspect of the disclosure, computer readable apparatusis described. In one embodiment, the apparatus includes a storage mediumconfigured to store one or more computer programs. In one embodiment,the apparatus includes a program memory or HDD or SDD on a computerizedcontroller device. In another embodiment, the apparatus includes aprogram memory, HDD or SSD on a computerized access node (e.g., CBSD).In yet another embodiment, the apparatus includes a program memory, HDDor SSD on a wireless-enabled mobile user device.

In a further aspect, a connection manager entity is disclosed. In oneembodiment, the connection manager comprises a computer programoperative to execute on a digital processor apparatus, and configuredto, when executed, obtain data relating to a quality of service orstrength of signal of each of (i) the MSO-provided CBRS service, and(ii) the MNO-provided cellular service, and cause selection of one overthe other based on the comparison. In one implementation, the connectionmanager entity (e.g., program) is disposed on a user mobile device(e.g., UE), and configured to autonomously perform the aforementionedobtainment of data and comparison, such as at the then-current locationof the UE. In another implementation, the connection manager entity isdisposed on an MSO network controller entity (i.e., a CBRS systemcontroller), and configured to evaluate the CBRS and MNO cellularoptions at one or more locations within a prescribed CBRS coverage area(e.g., via use of one or more base stations or eNBs).

In a further aspect of the present disclosure, business methods forenabling an alternative type of wireless connectivity to one or moreuser devices are provided. In one embodiment, the method(s) includeenabling temporary or ad hoc CBRS connectivity for a MNO subscriberhaving a cellular LTE subscription with the MNO, the MNO and theoperator of the CBRS network having a prescribed business relationship.

In another implementation, the inter-cell handovers are conducted inorder to maintain QoS (quality of service) requirements for usersapplications (or QoS policy invoked by the network operator or theroaming MNO user's MNO policies), and to minimize the disruption to therelevant MNO operator network cores.

In another aspect, a method of supplementing MNO licensed networkcoverage using quasi-licensed spectrum of an MSO is disclosed. In oneembodiment, the method includes operating a user device consistent witha first air interface protocol using licensed spectrum; determining aneed or desire to use the quasi-licensed spectrum; and based at least onthe determining, causing the user device to transition to a second airinterface protocol for communication via the quasi-licensed spectrum.User voice and/or data service is then established via the second airinterface between a CBSD and the user device, as well as at leastportions of the MSO and MNO cores.

These and other aspects shall become apparent when considered in lightof the disclosure provided herein.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a graphical illustration of prior art CBRS (Citizens BroadbandRadio Service) users and their relationship to allocated frequencyspectrum in the 3.550 to 3.700 GHz band.

FIG. 2 is a block diagram illustrating a general architecture for theCBRS system of the prior art.

FIG. 2a is a graphical representation of allocations for PAL versus GAAusers within the frequency band of FIG. 2.

FIG. 3a is a functional block diagram illustrating an exemplary hybridfiber network configuration useful with various aspects of the presentdisclosure.

FIG. 3b is a functional block diagram of an exemplary packetized contentnetwork architecture useful in conjunction with various principlesdescribed herein.

FIG. 4a is a functional block diagram of a first exemplary embodiment ofa quasi-licensed wireless network infrastructure useful with variousaspects of the present disclosure.

FIG. 4a -1 is a graphical representation of typical neutral host network(NHN), enterprise (private), and hybrid network architectures usefulwith various aspects of the present disclosure.

FIG. 4a -2 is a graphical representation of typical prior art 3GPP MNOand NHN network architecture.

FIG. 4a -3 is a graphical representation of a first exemplary embodimentof a software architecture useful with the architecture of FIG. 4 a.

FIG. 4a -4 is a graphical representation of a second exemplaryembodiment of a software architecture useful with the architecture ofFIG. 4 a.

FIG. 4a -5 is a block diagram illustrating one embodiment of an MSO/MNOCBRS network Architecture configured for MNO subscriber roaming to theMSO network.

FIG. 4b is a functional block diagram of a second exemplary embodimentof a wireless network infrastructure including distributed controllerfunctionality and client provisioning, useful with various aspects ofthe present disclosure.

FIG. 5 is logical flow diagram of an exemplary method for enablingroaming MNO subscriber connectivity via a quasi-licensed band (e.g.,CBRS) according to the present disclosure.

FIG. 5a is logical flow diagram of an exemplary implementation of amethod for MSO CBRS system bandwidth management according to the presentdisclosure.

FIG. 5b is logical flow diagram of an exemplary implementation of amethod for provisioning one or more UE data flows per MNO/MSO policies,according to the disclosure.

FIG. 6 is a ladder diagram illustrating a first embodiment of acommunication flow for establishing quasi-licensed band communicationfor a roaming MNO user in accordance with the methods of the presentdisclosure.

FIG. 7 is a functional block diagram illustrating a first exemplaryembodiment of an MSO CBRS controller apparatus useful with variousembodiments of the present disclosure.

All figures © Copyright 2017 Charter Communications Operating, LLC. Allrights reserved.

DETAILED DESCRIPTION

Reference is now made to the drawings wherein like numerals refer tolike parts throughout.

As used herein, the term “access node” refers generally and withoutlimitation to a network node which enables communication between a useror client device and another entity within a network, such as forexample a CBRS CBSD, a Wi-Fi AP, or a Wi-Fi-Direct enabled client orother device acting as a Group Owner (GO).

As used herein, the term “application” (or “app”) refers generally andwithout limitation to a unit of executable software that implements acertain functionality or theme. The themes of applications vary broadlyacross any number of disciplines and functions (such as on-demandcontent management, e-commerce transactions, brokerage transactions,home entertainment, calculator etc.), and one application may have morethan one theme. The unit of executable software generally runs in apredetermined environment; for example, the unit could include adownloadable Java Xlet™ that runs within the JavaTV™ environment.

As used herein, the terms “client device” or “user device” or “UE”include, but are not limited to, set-top boxes (e.g., DSTBs), gateways,modems, personal computers (PCs), and minicomputers, whether desktop,laptop, or otherwise, and mobile devices such as handheld computers,PDAs, personal media devices (PMDs), tablets, “phablets”, smartphones,and vehicle infotainment systems or portions thereof.

As used herein, the term “codec” refers to a video, audio, or other datacoding and/or decoding algorithm, process or apparatus including,without limitation, those of the MPEG (e.g., MPEG-1, MPEG-2,MPEG-4/H.264, H.265, etc.), Real (RealVideo, etc.), AC-3 (audio), DiVX,XViD/ViDX, Windows Media Video (e.g., WMV 7, 8, 9, 10, or 11), ATI Videocodec, or VC-1 (SMPTE standard 421M) families.

As used herein, the term “computer program” or “software” is meant toinclude any sequence or human or machine cognizable steps which performa function. Such program may be rendered in virtually any programminglanguage or environment including, for example, C/C++, Fortran, COBOL,PASCAL, assembly language, markup languages (e.g., HTML, SGML, XML,VoXML), and the like, as well as object-oriented environments such asthe Common Object Request Broker Architecture (CORBA), Java™ (includingJ2ME, Java Beans, etc.) and the like.

As used herein, the term “DOCSIS” refers to any of the existing orplanned variants of the Data Over Cable Services InterfaceSpecification, including for example DOCSIS versions 1.0, 1.1, 2.0, 3.0and 3.1.

As used herein, the term “headend” or “backend” refers generally to anetworked system controlled by an operator (e.g., an MSO) thatdistributes programming to MSO clientele using client devices. Suchprogramming may include literally any information source/receiverincluding, inter alia, free-to-air TV channels, pay TV channels,interactive TV, over-the-top services, streaming services, and theInternet.

As used herein, the terms “Internet” and “internet” are usedinterchangeably to refer to inter-networks including, withoutlimitation, the Internet. Other common examples include but are notlimited to: a network of external servers, “cloud” entities (such asmemory or storage not local to a device, storage generally accessible atany time via a network connection, and the like), service nodes, accesspoints, controller devices, client devices, etc.

As used herein, the term “LTE” refers to, without limitation and asapplicable, any of the variants or Releases of the Long-Term Evolutionwireless communication standard, including LTE-U (Long Term Evolution inunlicensed spectrum), LTE-LAA (Long Term Evolution, Licensed AssistedAccess), LTE-A (LTE Advanced), 4G LTE, WiMAX, and other wireless datastandards, including GSM, UMTS, CDMA2000, etc. (as applicable).

As used herein, the term “memory” includes any type of integratedcircuit or other storage device adapted for storing digital dataincluding, without limitation, ROM, PROM, EEPROM, DRAM, SDRAM, DDR/2SDRAM, EDO/FPMS, RLDRAM, SRAM, “flash” memory (e.g., NAND/NOR), 3Dmemory, and PSRAM.

As used herein, the terms “microprocessor” and “processor” or “digitalprocessor” are meant generally to include all types of digitalprocessing devices including, without limitation, digital signalprocessors (DSPs), reduced instruction set computers (RISC),general-purpose (CISC) processors, microprocessors, gate arrays (e.g.,FPGAs), PLDs, reconfigurable computer fabrics (RCFs), array processors,secure microprocessors, and application-specific integrated circuits(ASICs). Such digital processors may be contained on a single unitary ICdie, or distributed across multiple components.

As used herein, the terms “MSO” or “multiple systems operator” refer toa cable, satellite, or terrestrial network provider havinginfrastructure required to deliver services including programming anddata over those mediums.

As used herein, the terms “MNO” or “mobile network operator” refer to acellular, satellite phone, WMAN (e.g., 802.16), or other network serviceprovider having infrastructure required to deliver services includingwithout limitation voice and data over those mediums. The term “MNO” asused herein is further intended to include MVNOs, MNVAs, and MVNEs.

As used herein, the terms “network” and “bearer network” refer generallyto any type of telecommunications or data network including, withoutlimitation, hybrid fiber coax (HFC) networks, satellite networks, telconetworks, and data networks (including MANs, WANs, LANs, WLANs,internets, and intranets). Such networks or portions thereof may utilizeany one or more different topologies (e.g., ring, bus, star, loop,etc.), transmission media (e.g., wired/RF cable, RF wireless, millimeterwave, optical, etc.) and/or communications or networking protocols(e.g., SONET, DOCSIS, IEEE Std. 802.3, ATM, X.25, Frame Relay, 3GPP,3GPP2, LTE/LTE-A/LTE-U/LTE-LAA, WAP, SIP, UDP, FTP, RTP/RTCP, H.323,etc.).

As used herein, the term “network interface” refers to any signal ordata interface with a component or network including, withoutlimitation, those of the FireWire (e.g., FW400, FW800, etc.), USB (e.g.,USB 2.0, 3.0. OTG), Ethernet (e.g., 10/100, 10/100/1000 (GigabitEthernet), 10-Gig-E, etc.), MoCA, Coaxsys (e.g., TVnet™), radiofrequency tuner (e.g., in-band or OOB, cable modem, etc.),LTE/LTE-A/LTE-U/LTE-LAA, Wi-Fi (802.11), WiMAX (802.16), Z-wave, PAN(e.g., 802.15), or power line carrier (PLC) families.

As used herein, the term “QAM” refers to modulation schemes used forsending signals over e.g., cable or other networks. Such modulationscheme might use any constellation level (e.g. QPSK, 16-QAM, 64-QAM,256-QAM, etc.) depending on details of a network. A QAM may also referto a physical channel modulated according to the schemes.

As used herein, the term “server” refers to any computerized component,system or entity regardless of form which is adapted to provide data,files, applications, content, or other services to one or more otherdevices or entities on a computer network.

As used herein, the term “storage” refers to without limitation computerhard drives, DVR device, memory, RAID devices or arrays, optical media(e.g., CD-ROMs, Laserdiscs, Blu-Ray, etc.), or any other devices ormedia capable of storing content or other information.

As used herein, the term “Wi-Fi” refers to, without limitation and asapplicable, any of the variants of IEEE Std. 802.11 or related standardsincluding 802.11 a/b/g/n/s/v/ac or 802.11-2012/2013, as well as Wi-FiDirect (including inter alia, the “Wi-Fi Peer-to-Peer (P2P)Specification”, incorporated herein by reference in its entirety).

As used herein, the term “wireless” means any wireless signal, data,communication, or other interface including without limitation Wi-Fi,Bluetooth/BLE, 3G (3GPP/3GPP2), HSDPA/HSUPA, TDMA, CDMA (e.g., IS-95A,WCDMA, etc.), FHSS, DSSS, GSM, PAN/802.15, WiMAX (802.16), 802.20,Zigbee®, Z-wave, narrowband/FDMA, OFDM, PCS/DCS,LTE/LTE-A/LTE-U/LTE-LAA, analog cellular, CDPD, satellite systems,millimeter wave or microwave systems, acoustic, and infrared (i.e.,IrDA).

Overview

In one exemplary aspect, the present disclosure provides improvedmethods and apparatus for wireless network access using, for example,“quasi-licensed” spectrum such as that provided by the recent CBRStechnology initiatives. In an exemplary implementation, a networkarchitecture is provided which leverages an MSO's extant distributionand backhaul capability to collect and exchange metrics between SAS,access networks (comprising of CBRS and other bands), accesstechnologies such as LTE and Wi-Fi), DOCSIS and core networks, andexecute a control and optimization function to enhance performance anduser experience to its subscribers (and even non-subscriber “ad hoc”users), or provide wireless coverage where it would be otherwise notavailable, or in a complementary or parallel fashion to extant cellularor mobile service provided by “partnered” or cooperating Mobile (macro)Network Operators (MNOs), including for faster data rates in certainscenarios.

Additionally, differentiation among multiple services provided to users(whether MNO or MSO subscribers) is afforded via a policy engine(server), in light of (i) business agreements between the MSO and MNO(s)(ii) pre-defined services which require certain differentiated resourceallocations, and (iii) input from analytics processes to support theformulation and implementation of the policies.

In one implementation, extant TD-LTE (Long Term Evolution) technology isleveraged within the available CBRS band(s) for improved venue (e.g.,in-building) coverage and capacity augmentation for other unlicensedsystems operating in other bands such as Wi-Fi, and/or for MNO-basedlicensed systems (e.g., to provide coverage where the MNO cannot via itslicensed spectrum, or to provide a complementary or alternative serviceto the MNO-provided licensed spectrum services). This provides thenetwork operator (e.g., MSO) and its users with a number of benefits,including inter alia: (i) obviating any need to adopt custom technology(e.g., a new air interface, and the new user mobile devices and MSOinfrastructure that are necessitated thereby); (ii) reduced interference(and hence better user experience) due to less “crowding” in the lightlyused CBRS quasi-licensed bands; and (iii) a complementary or “fallback”capability to the MNO's cellular coverage (as well as the MSO's extantWLAN services), such that the MNO user can be connected to the MNO core(and hence other MNO and non-MNO endpoints) via the MSO's quasi-licensedCBRS access points (i.e., CBSDs).

Additionally, the present disclosure provides methods and correspondingarchitecture to optimize and share a common CBRS small-cell cluster withone or more of the partnered/cooperating MNOs, including use ofdifferent priorities and/or service (e.g., QoS) requirements fordifferent user traffic types (e.g., video/audio/data etc.). Moreover, inanother implementation, traffic originating from and/or destined todifferent MNO partners can be prioritized or otherwise heterogeneouslytransacted based on e.g., agreements between the MSO and the variousMNOs. This prioritization structure and/or heterogeneous treatment canfurther be extended across the MSO core and distribution network.

The MSO can advantageously leverage its high-bandwidth backhaulcapabilities for the CBRS small-cells, whether for use by the MSO or itsMNO partners. For instance, data to/from MNO subscribers present withinan MSO-serviced CBRS cell may be “fast tracked” as compared to othernon-MNO users. Moreover, cross-network optimizations can beaccomplished, in effect treating the MSO and MNO networks as a commonnetwork for purposes of roaming MNO subscriber support.

Extant subscribers of the CBRS network can also “camp” on an MNO networkfor certain services which may not be offered by the CBRS provider (e.g.voice service), and CBRS network subscribers may utilize an MNO partnernetwork for both voice and data when in a given geographic location thatdoes not have any CBRS coverage.

Detailed Description of Exemplary Embodiments

Exemplary embodiments of the apparatus and methods of the presentdisclosure are now described in detail. While these exemplaryembodiments are described in the context of the previously mentionedwireless access points (e.g., CBSDs and WLAN APs) associated with amanaged network (e.g., hybrid fiber coax (HFC) cable architecture havinga multiple systems operator (MSO), digital networking capability, IPdelivery capability, and a plurality of client devices), the generalprinciples and advantages of the disclosure may be extended to othertypes of radio access technologies (“RATs”), networks and architecturesthat are configured to deliver digital data (e.g., text, images, games,software applications, video and/or audio). Such other networks orarchitectures may be broadband, narrowband, or otherwise, the followingtherefore being merely exemplary in nature.

It will also be appreciated that while described generally in thecontext of a network providing service to a customer or consumer or enduser or subscriber (i.e., within a prescribed venue, or other type ofpremises), the present disclosure may be readily adapted to other typesof environments including, e.g., outdoors, commercial/retail, orenterprise domain (e.g., businesses), or even governmental uses, such asthose outside the proscribed “incumbent” users such as U.S. DoD and thelike. Yet other applications are possible.

Also, while certain aspects are described primarily in the context ofthe well-known Internet Protocol (described in, inter alia, InternetProtocol DARPA Internet Program Protocol Specification, IETF RCF 791(September 1981) and Deering et al., Internet Protocol, Version 6 (IPv6)Specification, IETF RFC 2460 (December 1998), each of which isincorporated herein by reference in its entirety), it will beappreciated that the present disclosure may utilize other types ofprotocols (and in fact bearer networks to include other internets andintranets) to implement the described functionality.

Moreover, while the current SAS framework is configured to allocatespectrum in the 3.5 GHz band (specifically 3,550 to 3,700 MHz), it willbe appreciated by those of ordinary skill when provided the presentdisclosure that the methods and apparatus described herein may beconfigured to utilize other “quasi licensed” or other spectrum,including without limitations above 4.0 GHz (e.g., currently proposedallocations up to 4.2 GHz).

Moreover, while described in the context of exemplary LTE (3GPP) basedair interface technologies, it will be appreciated that the variousaspects of the present disclosure may be adapted to other airinterfaces, including for example non-OFDM air interfaces such asDSSS/CDMA, FHSS, and FDMA/TDMA.

Other features and advantages of the present disclosure will immediatelybe recognized by persons of ordinary skill in the art with reference tothe attached drawings and detailed description of exemplary embodimentsas given below.

Service Provider Network—

FIG. 3a illustrates a typical service provider network configurationuseful with the features of the CBRS-based wireless network(s) describedherein. This service provider network 300 is used in one embodiment ofthe disclosure to provide backbone and Internet access from the serviceprovider's wireless access nodes (e.g., CBSDs, Wi-Fi APs or basestations 314 operated or maintained by the service provider or itscustomers/subscribers), one or more stand-alone or embedded cable modems(CMs) 312, 313 in data communication therewith, or even third partyaccess points accessible to the service provider via, e.g., aninterposed network such as the Internet 311 (e.g., with appropriatepermissions from the access node owner/operator/user).

As described in greater detail subsequently herein with respect to FIG.4a , one or more controllers 310 are utilized for, inter alia, controlof the wireless network access nodes 314 at least partly by the MSO. Asopposed to an unmanaged network, the managed service-provider network300 of FIG. 3a advantageously allows, inter alia, control and managementof a given user's access (such user which may be a network subscriber,or merely an incidental/opportunistic user of the service) via thewireless access node(s) 314, including imposition and/or reconfigurationof various access “rules” or other configurations applied to thewireless access nodes. For example, the service provider network 300allows components at an indoor venue of interest (e.g., CBSDs, Wi-Fi APsand any supporting infrastructure such as routers, switches, etc.) to beremotely reconfigured by the network MSO, based on e.g., prevailingoperational conditions in the network, changes in user population and/ormakeup of users at the venue, business models (e.g., to maximizeprofitability or provide other benefits such as enhanced userexperience, as described infra), spectrum channel changes orwithdrawals, or even simply to enhance user experience using one RAT(e.g., CBRS) when another RAT (e.g., WLAN is sub-optimal for whateverreason).

In certain embodiments, the service provider network 300 alsoadvantageously permits the aggregation and/or analysis of subscriber- oraccount-specific data (including inter alia, particular mobile devicesassociated with such subscriber or accounts) as part of the provision ofservices to users under the exemplary delivery models described herein.As but one example, device-specific IDs (e.g., MAC address or the like)can be cross-correlated to MSO subscriber data maintained at e.g., thenetwork head end(s) 307 so as to permit or at least facilitate, amongother things, (i) user authentication; (ii) correlation of aspects ofthe event or venue to particular subscriber demographics, such as fordelivery of targeted advertising; and (iii) determination ofsubscription level, and hence subscriber privileges and access tocontent/features. Moreover, device profiles for particular user devicescan be maintained by the MSO, such that the MSO (or its automated proxyprocesses) can model the user device for wireless capabilities.

The wireless access nodes 314 disposed at the service location(s) (e.g.,venue(s) of interest) can be coupled to the bearer managed network 300(FIG. 3a ) via, e.g., a cable modem termination system (CMTS) andassociated local DOCSIS cable modem (CM) 312, 313, a wireless bearermedium (e.g., an 802.16 WiMAX or millimeter wave system—not shown), afiber-based system such as FiOS or similar, a third-party medium whichthe managed network operator has access to (which may include any of theforegoing), or yet other means.

The various components of the exemplary embodiment of the network 300generally include (i) one or more data and application originationsources 302; (ii) one or more content sources 303, (iii) one or moreapplication distribution servers 304; (iv) one or more video-on-demand(VOD) servers 305, (v) client devices 306, (vi) one or more routers 308,(vii) one or more wireless access node controllers 310 (may be placedmore locally as shown or in the headend or “core” portion of network),(viii) one or more cable modems 312, 313, and/or (ix) one or more accessnodes 314. The application server(s) 304, VOD servers 305 and clientdevice(s) 306 are connected via a bearer (e.g., HFC) network 301. Asimple architecture comprising one of each of certain components 302,303, 304, 305, 308, 310 is shown in FIG. 3a for simplicity, although itwill be recognized that comparable architectures with multipleorigination sources, distribution servers, VOD servers, controllers,and/or client devices (as well as different network topologies) may beutilized consistent with the present disclosure.

It is also noted that cable network architecture is typically a“tree-and-branch” structure, and hence multiple tiered access nodes 314(and other components) may be linked to each other or cascaded via suchstructure.

FIG. 3b illustrates an exemplary high-level MSO network architecture forthe delivery of packetized content (e.g., encoded digital contentcarried within a packet or frame structure or protocol) that may beuseful with the various aspects of the present disclosure. In additionto on-demand and broadcast content (e.g., live video programming), thesystem of FIG. 3b may deliver Internet data and OTT (over-the-top)services to the end users (including those of the access nodes 314) viathe Internet protocol (IP) and TCP, although other protocols andtransport mechanisms of the type well known in the digital communicationart may be substituted.

The network architecture 320 of FIG. 3b generally includes one or moreheadends 307 in communication with at least one hub 317 via an opticalring 337. The distribution hub 317 is able to provide content to varioususer/client devices 306, and gateway devices 360 as applicable, via aninterposed network infrastructure 345.

As described in greater detail below, various content sources 303, 303 aare used to provide content to content servers 304, 305 and originservers 321. For example, content may be received from a local,regional, or network content library as discussed in co-owned U.S. Pat.No. 8,997,136 entitled “APPARATUS AND METHODS FOR PACKETIZED CONTENTDELIVERY OVER A BANDWIDTH-EFFICIENT NETWORK”, which is incorporatedherein by reference in its entirety. Alternatively, content may bereceived from linear analog or digital feeds, as well as third partycontent sources. Internet content sources 303 a (such as e.g., a webserver) provide Internet content to a packetized content originserver(s) 321. Other IP content may also be received at the originserver(s) 321, such as voice over IP (VoIP) and/or IPTV content. Contentmay also be received from subscriber and non-subscriber devices (e.g., aPC or smartphone-originated user made video).

The centralized media server(s) 321, 304 located in the headend 307 mayalso be replaced with or used in tandem with (e.g., as a backup) to hubmedia servers (not shown) in one alternative configuration. Bydistributing the servers to the hub stations 317, the size of the fibertransport network associated with delivering VOD services from thecentral headend media server is advantageously reduced. Multiple pathsand channels are available for content and data distribution to eachuser, assuring high system reliability and enhanced asset availability.Substantial cost benefits are derived from the reduced need for a largecontent distribution network, and the reduced storage capacityrequirements for hub servers (by virtue of the hub servers having tostore and distribute less content).

It will also be recognized that a heterogeneous or mixed server approachmay be utilized consistent with the disclosure. For example, one serverconfiguration or architecture may be used for servicing cable,satellite, etc., subscriber CPE-based session requests (e.g., from auser's DSTB or the like), while a different configuration orarchitecture may be used for servicing mobile client requests.Similarly, the content servers 321, 304 may either besingle-purpose/dedicated (e.g., where a given server is dedicated onlyto servicing certain types of requests), or alternatively multi-purpose(e.g., where a given server is capable of servicing requests fromdifferent sources).

The network architecture 320 of FIG. 3b may further include a legacymultiplexer/encrypter/modulator (MEM; not shown). In the presentcontext, the content server 304 and packetized content server 321 may becoupled via a LAN to a headend switching device 322 such as an 802.3zGigabit Ethernet (or “10G”) device. For downstream delivery via the MSOinfrastructure (i.e., QAMs), video and audio content is multiplexed atthe headend 307 and transmitted to the edge switch device 338 (which mayalso comprise an 802.3z Gigabit Ethernet device) via the optical ring337.

In one exemplary content delivery paradigm, MPEG-based video content(e.g., MPEG-2, H.264/AVC) may be delivered to user IP-based clientdevices over the relevant physical transport (e.g., DOCSIS channels);that is as MPEG-over-IP-over-MPEG. Specifically, the higher layer MPEGor other encoded content may be encapsulated using an IP network-layerprotocol, which then utilizes an MPEG packetization/container format ofthe type well known in the art for delivery over the RF channels orother transport, such as via a multiplexed transport stream (MPTS). Inthis fashion, a parallel delivery mode to the normal broadcast deliveryexists; e.g., in the cable paradigm, delivery of video content both overtraditional downstream QAMs to the tuner of the user's DSTB or otherreceiver device for viewing on the television, and also as packetized IPdata over the DOCSIS QAMs to the user's PC or other IP-enabled devicevia the user's cable modem 312 (including to end users of the accessnode 314). Delivery in such packetized modes may be unicast, multicast,or broadcast.

Delivery of the IP-encapsulated data may also occur over the non-DOCSISQAMs, such as via IPTV or similar models with QoS applied.

Individual client devices such as cable modems 312 and associatedend-user devices 306 a, 306 b of the implementation of FIG. 3b may beconfigured to monitor the particular assigned RF channel (such as via aport or socket ID/address, or other such mechanism) for IP packetsintended for the subscriber premises/address that they serve. The IPpackets associated with Internet services are received by edge switch,and forwarded to the cable modem termination system (CMTS) 339. The CMTSexamines the packets, and forwards packets intended for the localnetwork to the edge switch. Other packets are in one variant discardedor routed to another component.

The edge switch forwards the packets receive from the CMTS to the QAMmodulator, which transmits the packets on one or more physical(QAM-modulated RF) channels to the client devices. The IP packets aretypically transmitted on RF channels that are different than the “inband” RF channels used for the broadcast video and audio programming,although this is not a requirement. As noted above, the premises devicessuch as cable modems 312 are each configured to monitor the particularassigned RF channel (such as via a port or socket ID/address, or othersuch mechanism) for IP packets intended for the subscriberpremises/address that they serve.

In one embodiment, both IP data content and IP-packetized audio/videocontent is delivered to a user via one or more universal edge QAMdevices 340. According to this embodiment, all of the content isdelivered on DOCSIS channels, which are received by a premises gateway360 or cable modem 312, and distributed to one or more respective clientdevices/UEs 306 a, 306 b, 306 c in communication therewith.

In one implementation, the CM 312 shown in FIG. 3b services a venue,such as a conference center or hospitality structure (e.g., hotel),which includes a CBRS node 314 a for CBRS-band (3.5 GHz) access, and aWLAN (e.g., Wi-Fi) node 314 b for WLAN access (e.g., within 2.4 GHz ISMband). Notably, the client devices 306 c communicating with the accessnodes 314 a, 314 b, as described in greater detail subsequently herein,can utilize either RAT (CBRS or WLAN) depending on, inter alia,directives received from the MSO controller 310 (FIG. 3a ) via oneaccess node 314 or the other, or even indigenous logic on the clientdevice 306 c enabling it to selectively access one RAT or the other.Feasibly, both RATs could operate in tandem, since they utilizedifferent frequencies, modulation techniques, interference mitigationtechniques, Tx power, etc.

In parallel with (or in place of) the foregoing delivery mechanisms, theMSO backbone 331 and other network components can be used to deliverpacketized content to the user's mobile client device 306 c via non-MSOnetworks. For example, so-called “OTT” content (whether tightly coupledor otherwise) can be ingested, stored within the MSO's networkinfrastructure, and delivered to the user's mobile device via aninterposed ISP (Internet Service Provider) network and public Internet311 (e.g., at a local coffee shop, via a Wi-Fi AP connected to thecoffee shop's ISP via a modem, with the user's IP-enabled end-userdevice 306 c utilizing an Internet browser or MSO/third-party app tostream content according to an HTTP-based approach).

Wireless Services Architecture—

FIG. 4a illustrates an exemplary embodiment of a network architecture400 useful in implementing the CBRS-based wireless RAT access and MNOroaming methods of the present disclosure. As used in the presentcontext, the term “users” may include without limitation end users(e.g., individuals, whether subscribers of the MSO network, the MNOnetwork, or other), venue operators, third party service providers, oreven entities within the MSO itself (e.g., a particular department,system or processing entity).

As shown, the architecture generally includes an MSO-maintained CBRScontroller 310 (which may be disposed remotely at the backend or headendof the system within the MSO domain as shown or at the served venue, orat an intermediary site), a CBRS Core/Neutral Host/Private NetworkController 413, a deep packet inspection (DPI)/analytics engine 413 indata communication with the CBRS controller 310, an MSO-maintainedsubscriber and CBRS database 404, one or more CBSD access nodes 314 indata communication with the CBRS controller 310 (e.g., via existingnetwork architectures including any wired or wireless connection), aswell as any number of client devices 306 c (smartphones, laptops,tablets, watches, vehicles, etc.). The CBSD 314 includes in theillustrated embodiment an embedded cable modem 312 used forcommunication with a corresponding CMTS 339 (FIG. 3b ) within the MSO's(e.g., cable) plant 300 via cable power and backhaul infrastructure 406,including high-data bandwidth connections to the MSO's backbone 331, andelectrical power for the CBSD A MNO (mobile network operator) network411 also communicates with the MSO network via the backhaul 406, such asfor inter-operator communications regarding common users/subscribers.

In the present context, a Neutral-Host-Network (NHN) is a Radio AccessNetwork (RAN) deployed in 3.5 GHz band, with an associated NHN core. Forinstance, in one implementation, the MSO acts as an NHN provider via,inter alia, its provision of the CBRS RAN. As shown in FIG. 4a -1, boththe NHN RAN and core may be used to provide/offer services to thesubscribers of the MSO's MNO partners, including access to the MNO corevia the NHN (MSO) RAN and core.

Conversely, in a private network (or enterprise network) (also shown inFIG. 4a -1), a private entity uses the RAN (e.g., CBRS-based RAN) forits own exclusive use, exclusive of any MNO partners or theirsubscribers.

In a hybrid network (see again FIG. 4a -1), a CBRS core and RAN canserve UEs having multiple subscriptions (e.g., for the private orenterprise MSO, and the cellular MNO) to provide both the enterprise aswell as MNO services through the common CBRS RAN and core.

In the present context (i.e., CBRS RAN), the neutral host network (NHN)can be implemented as another LTE network by an entity different thanthe MNO (i.e., the MSO or a proxy thereof), in contrast to conventional3GPP architectures (see FIG. 4a -2) wherein an NHN gateway (NHN-GW;connected to the packet data network gateway (PDN-GW) of the MNO in FIG.4a -2), can interface with any access network. For instance, in oneimplementation according to the present disclosure, traffic originatingfrom/destined to any of the MNO partner networks may be prioritized andprovided differentiated treatment within the MSO CBRS network (suchdifferentiation with a RAN based on, inter alia, MNO partner identitynot being supported in the prior art architecture shown). Additionally,different types of traffic (voice/video/data etc.) may be provideddifferent treatment with in the CBRS network, across the MSO (e.g.,cable) network in the backhaul, and across the relevant MNO partnerinterface, as well as being differentiated between different MNOpartners. The optimization of this traffic to/from multitude of MNOpartners may be based on network policies, agreements with MNOs, networkanalytics across CBRS RAN, CBRS core and MNO operator interfaces.

Referring again to FIG. 4a , in operation, the Domain Proxy (DP) 208 isin logical communication with the CBSD disposed at the venue (eitherdirectly, as shown, or via MSO backend network infrastructure) and theMSO CBRS controller 310. The DP 208 provides, inter alia, FSAS interfacefor the CBSD, including directive translation between CBSD 314 and FSAScommands, bulk CBSD directive processing, and interference contributionreporting to the FSAS (i.e., to help an SAS tune or update itspredictive propagation models and detect realistic interference issuesonce CBSDs are deployed, the CBSDs can provide signal strength andinterference level measurements).

The MSO controller 310 in the illustrated embodiment communicates withthe DP 208 via an MSO CBRS access network 410, which may be a publicinternetwork (e.g., the Internet), private network, or other, dependingon any security and reliability requirements mandated by the MSO and/orSAS.

As previously noted, a CBRS “domain” is defined is any collection ofCBSDs 314 that need to be grouped for management; e.g.: largeenterprises, venues, etc. The DP 208 aggregate control information flowsto the FSAS1 202 and/or any participating Commercial SAS (CSAS) 420, andgenerate performance reports, channel requests, heartbeats, and othertypes of data. In the illustrated embodiment, the DP 208 is operated bya third-party service provider, although it will be appreciated that theMSO may operate and maintain the DP 208, and or operate/maintain its owninternal DP (as in FIG. 4b ), such as for channel request processing,aggregation, reporting, and other of the above-listed functions for theMSO's internal CBRS domains, for interface with an external DP 208.

The MSO controller 310 communicates logically with the DPI server engine413, as well as the MSO core function 412 as shown in FIG. 4a -3. In oneembodiment, the MSO core 412 further communicates with the MNO core 411,such as via an application or other computer program operative withinthe relevant MNO core entity. Also as shown in FIG. 4a -3, the MNO core411 controls the link layer/PHY of the UE (i.e., via LTE-FDD signalingand operation between an eNB of the MNO network and the UE), such thatthe UE PHY can be configured to, inter alia, scan the relevant 3.5 GHzband(s) for energy in support of UE “entry” into the MSO CBRS RAN, andoperate within the CBRS RAN in LTE-TDD mode. This approach requires atleast some level of communication between the UE and its home MNOnetwork (or at least another MNO network which it is visiting which canmaintain an LTE-FDD link to an eNB); once the UE loses contact with thehome or visited LTE-FDD (cellular) network, it will not be able to enterthe MSO CBRS RAN (at least without prior configuration of its RFfunctions to do so).

FIG. 4a -4 illustrates another exemplary software architecture accordingto the disclosure. In this embodiment, the UE includes a CBRS clientapplication, which is communicative with the CBRS controller applicationvia the CBSD (e.g., via a client portion of the CBRS controller app.installed on the CBSD). This way, the CBRS UE functionality (includingany software-defined radio functions such as retuning or configuring theUE RF front end for the CBRS 3.5 GHz band(s)) can be invoked by the MSOnetwork directly, rather than through MNO UE/EUTRAN core functionality(e.g., while the UE is communcative with the MNO eNB as described abovewith respect to FIG. 4a -3).

Returning again to FIG. 4a , the MSO subscriber and CBRS database 404includes several types of data useful in operation of the system 400. Aspart thereof, a client device database not shown is also provided,wherein the MSO CBRS controller 310 can access and store data relatingto, inter alia: (i) individual client devices, such as MAC address orother specific identifying information, (ii) any associated subscriberaccounts or records, (iii) the LTE (and optionally WLAN) configurationof the client, supported LTE/Wi-Fi variants, MCS, MIMO capability, etc.

The client database may also optionally include the multi-RATprovisioning status of the particular client (e.g., whether the clienthas had a connection manager (CM) application installed, status of“pushed” configuration data to the installed CM, etc.). As described ingreater detail below with respect to FIG. 4b , one implementation of theCBRS system of the present disclosure utilizes MSO-provisioned clientdevice CM apps which enable the client device to configure and manageits various air interfaces (including WLAN, CBRS-LTE, and non-CBRS LTE).Also, client-provided and MNO-provided data on roaming users may bemaintained within the CBRS client DB 404.

The MSO database 404 also includes a CBRS database, which in theillustrated embodiment retains data relating to, among other things: (i)CBSD identification (e.g., MAC), (ii) CBSD location, (iii) associationwith parent or child nodes or networks (if any), and (iv) CBRSconfiguration and capabilities data. The CBRS database 404 may alsoinclude MSO-maintained data on spectrum usage and historical patterns,channel withdrawals, and other data which enable the MSO to proactively“plan” channel usage and allocation within the venue(s) of interestwhere the CBSD(s) 314 operate.

The MSO CBRS controller 310 includes, inter alia, optimization functionswhich take into consideration network state and topology, (e.g., foraccess networks spanning across multiple access bands and technologies,cable backhaul and the core network, such as where a 2.4 GHz Wi-Fiaccess network together with 2.5 GHZ and 3.5 Ghz LTE network, cablebackhaul and MSO (cable) core together can be optimized), loading, anduser requirements, and generate standardized requests to the FSAS1 202or CSAS1 420 services via the DP 208. The controller 310 also “tunes”the response from FSAS/CSAS before sending it to the CBSDs 314.Specifically, in one particular implementation, mobility optimization isperformed by the controller 310 by taking FSAS/CSAS channel change,withdrawal, and power change, and other self-optimizing network (SON)functions into account, as described in greater detail subsequentlyherein. The FSAS/CSAS response is first analyzed by the controller logicas to the number of affected downstream devices (e.g., how many smallcells or other CBSDs are affected), and the instructions sent to theindividual CBSDs in phases/groups, or according to some other scheme soas to mitigate the impact on the UEs (yet consistent with FSAS/CSAS andCBRS system requirements). In this fashion, an individual UE can be“moved around” to other CBSDs and/or frequency bands to the extentpossible, and user experience preserved (i.e., little or nodiscontinuity in service is perceived).

In certain embodiments, each CBSD 314 is located within and/or servicesone or more areas within one or more venues (e.g., a building, room, orplaza for commercial, corporate, academic purposes, and/or any otherspace suitable for wireless access). Each CBSD 314 is configured toprovide wireless network coverage within its coverage or connectivityrange. For example, a venue may have a wireless modem installed withinthe entrance thereof for prospective customers to connect to, includingthose in the parking lot via inter alia, their LTE-enabled vehicles orpersonal devices of operators thereof Notably, different classes of CBSD314 (e.g., eNB) may be utilized. For instance, Class A eNBs can transmitup 30 dbm (1 watt), while Class-B eNBs can transmit up to 50 dbm, so theaverage area can vary widely. In practical terms, a Class-A device mayhave a working range on the order of hundreds of feet, while a Class Bdevice may operate out to thousands of feet or more, the propagation andworking range dictated by a number of factors, including the presence ofRF or other interferers, physical topology of the venue/area, energydetection or sensitivity of the receiver, etc.

In the exemplary embodiment, one or more CBSDs 314 may be indirectlycontrolled by the CBRS controller 310 (i.e., via infrastructure of theMSO network), or directly controlled by a local or “client” CBRScontroller disposed at the venue (not shown). Various combinations ofthe foregoing direct and indirect control may be implemented within thearchitecture 400 of FIG. 4a as desired. The controller 310 isimplemented in this instance as a substantially unified logical andphysical apparatus maintained within the MSO domain, such as at an MSOheadend or hubsite, and in communication with the MNO core 411 via theMSO core function 412. In the embodiment of FIG. 4a , the controller 310is configured to at least: (i) dynamically monitor RF conditions andperformance information in the hosting environment via use of the CBSDs314 a; (ii) cause issuance of interference reports based on the data of(i) for transmission to the DP 208 (and forwarding to the FSAS/CSAS)(iii) cause issuance of spectrum requests to the DP 208 (for forwardingto the cognizant FSAS 202 or CSAS 420), as well as implementing the QoSand policy functions for the roaming MNO users as described in greaterdetail below.

The controller 310 also optionally includes algorithms to optimizeoperation of the “local” CBRS network maintained by the MSO, such aswithin a target venue or area. These optimizations may include forexample: (a) utilization of the environmental interference data of (i)above to characterize the CBRS band(s) of the venue/area; (b) use thecharacterization of (a) to structure requests for spectrum allocationwithin the CBRS band(s) to the DP/SAS (e.g., which will mitigateinterference or contention within the venue/are in those bands); (c) usethe interference data of (i) above, and other relevant data (e.g.,attendance, time, interference/signal as a function of CBSD location,etc.) to build historical profiles of spectrum use a function of variousvariables, including profiles particular to the venue/area itself, asdescribed in co-pending U.S. patent application Ser. No. 15/612,630filed Jun. 2, 2017 entitled “APPARATUS AND METHODS FOR PROVIDINGWIRELESS SERVICE IN A VENUE,” incorporated herein by reference in itsentirety; (d) utilize data regarding spectrum availability withdrawals(e.g., where DoD assets require use of a previously allocated band) andother events to generate predictive or speculative models on CBRS bandutilization as a function of time.

In addition to the foregoing, the controller 310 may be configured toactively or passively coordinate MSO user/subscriber RAT and bandallocations between CBSDs (using CBRS allocated spectrum atapproximately 3.5 GHz) and e.g., Wi-Fi use of 2.4 or 5 GHz bands of ISM,so as to optimize user experience, as described in greater detail belowwith respect to FIG. 4c . See, e.g., the exemplary methods and apparatusdescribed in co-pending and co-owned U.S. patent application Ser. No.15/677,940 previously incorporated herein.

In the exemplary embodiment, optimization functions within the MSOcontroller 310 takes into consideration (i) network state (both MSO andMNO networks), (ii) MSO small cell network topology, (iii) current MSOsmall cell network load, and (iv) user-specific requirements, andgenerate a standardized request to the SAS service based thereon (the“standardization” refers to the protocols/request mechanism used incontacting the SAS). The optimization functions of the controller 310also “tune” the response from the SAS entity before sending it to theCBSD 314 and MNO Core 412 (see FIGS. 4a and 6). For instance, the SASmay allocate certain resources for certain periods of time, which may beyet further optimized by the controller 310 for particulars of the MSOCBRS RAN (e.g., known problematic frequency bands deleted from theallocation, etc.). In one implementation, the aforementioned tuningincludes adjusting the transmission power of each individual small cellin the CBRS network while adhering to the maximum limits mandated bySAS, taking into account load in terms of both (i) amount of trafficcarried, and (ii) number of users served by each individual cell in theCBRS network. Based on this information, users from the MNO partner canbe accepted, rejected at a given small cell within the CBRS network,and/or migrated to other cells).

Moreover, such tuning can include correlating QoS policies orrequirements applied to individual services (e.g., uplink/downlinkthroughput) to subscriber profiles, such that subscribers receiveservices commensurate with their subscription plans and/or otherrequirements. Allocation of other resources within the MSO/MNO networkbased on the aforementioned user profiles may also be employed, such ase.g., where packet routing algorithms are implemented in order tominimize latency within (at least) the MSO portion of the network.

Moreover, mobility optimization functions within the controller 310 takeSAS allocations/changes, SON (self optimizing network) functions andpolicies, as well as priorities of different traffic types(voice/video/data, etc.) to/from MNO cores. Moreover, priorities of agiven MNO and its users in the context of the CBRS operator (e.g., MSO),as well as the DPI analytics data generated by the DPI/analytics engine413, are taken into account by the optimization functions of thecontroller. In one implementation, the optimization is a combination oftwo or more metrics, e.g. (i) maximization of the user/device density inthe small cell network (i.e., user/devices per geographical area, or pereNB); (ii) maximization of data throughput in the network within theuplink and/or downlink(s) (iii) adherence to applicable service levelagreement(s) (SLA(s)) for QoS for different critical services (e.g.,conversation voice, audio/video streaming, or live video); and (iv)compliance with one or more service policies of MNO or MSO networks,which may include e.g., allocating resources to certain high-value usersor services to comply with the SLA per the policy or policies.

As an aside, deep packet inspection (DPI, also known as complete packetinspection and information extraction) is a form of computer networkpacket filtering that examines portions of a digital data packet withregard to various criteria or attributes. For example, malware such asviruses, protocol non-compliance, and network intrusions can ostensiblybe detected using DPI techniques, such as to decide whether the packetmay continue further processing within the network, or should be routedto a different destination (such as for cleansing, collection ofstatistical information, etc.). See, e.g., co-owned and copending U.S.patent application Ser. No. 15/043,361 filed Feb. 12, 2016 and entitled“APPARATUS AND METHODS FOR MITIGATION OF NETWORK ATTACKS VIA DYNAMICRE-ROUTING”, incorporated herein by reference in its entirety, wherein abackbone provider's ingress and egress peer routers which route trafficaccording to “path”-routed schemes can be leveraged in the context ofmitigating network-based attacks; path-based routing can be manipulatedin a manner that is not subject to the same network routing loopconstraints as hop-based routing.

Multiple headers for IP packetized data exist; however, networkequipment only needs to use the first of these (i.e., the IP header) fornormal packet routing operations. Use of additional headers (such asthose of underlying TCP or UDP protocols commonly used in conjunctionwith the IP network-layer protocol) is normally considered to be shallowpacket inspection (aka “stateful” packet inspection), whereas furtheranalysis is required for so-called DPI.

Exemplary techniques for performing such deep packet inspection (DPI)are described in, for example, U.S. Pat. No. 9,413,651 entitled“SELECTIVE DEEP PACKET INSPECTION,” U.S. Pat. No. 9,166,891 entitled“POLICY-ENABLED DYNAMIC DEEP PACKET INSPECTION FOR TELECOMMUNICATIONSNETWORKS,” and U.S. Pat. No. 8,189,465 entitled “DEEP PACKET INSPECTIONPOLICY ENFORCEMENT”, each of the foregoing incorporated herein byreference in its entirety.

In another implementation, the DPI is used to enforce certain networkservice level metrics, such as voice MOS (DEFINE PLEASE) score,streaming video quality metrics, network load adherence, and/or supportfor emergency services.

As part of the provisioning process for prioritization of certainclass(es) of users and/or services (voice, streaming audio/video, livestreaming etc.), QoS characteristics and resource reservations on theMSO backhaul and CBRS RAN for one or more MNO user policies (e.g., QoSin CBRS LTE RAN and core based on different LTE QoS Class Identifiersand further refined based on agreements with different MNO partners) arecreated within the MSO policy servers/enforcers 455, which provide thecreated policies to the DPI/analytics engine 413 for enforcement asdescribed subsequently herein. For instance, in the exemplary context ofLTE, there are multiple different QCIs (1 through 9) which are used foroperational support of different types of QoS depending on the type ofbearer (see Tables 4 and 5 below):

TABLE 4 LTE QoS GBR Non-GBR QoS Class Identifier Supported SupportedAllocation and Retention Priority Supported Supported Guaranteed Bitrate (GBR) Supported Maximum Bit rate (MBR) Supported APN AggregateMaximum Bit rate Supported UE Aggregate Maximum Bit rate Supported

TABLE 5 Packet Packet Error LTE Delay Loss QCI Type Priority Budget RateTypical Services QCI-1 GBR 2 100 ms 10⁻² Conversational voice QCI-2 4150 ms 10⁻³ Live streaming of conversational voice QCI-3 3  50 ms Realtime gaming QCI-4 5 300 ms 10⁻⁶ Video (buffered streaming) QCI-5 Non- 1100 ms IMS signaling QCI-6 GBR 6 300 ms Video (buffered streaming), TCPbased applications QCI-7 7 100 ms 10⁻³ Voice, video (live streaming),interactive gaming QCI-8 8 300 ms 10⁻⁶ Video (buffered streaming), QCI-99 TCP based applications

These policies can be user and/or service—specific, and may vary betweendifferent MNO partners for a given MSO/CBRS provider.

The DPI/analytics engine server 413 also in one embodiment, triggers oneor more deep packet inspection processes to serve the roaming MNO usersmatching a specified QoS profile (e.g., a set of QoS characteristicswhich are complied with in the CBRS RAN, backhaul, core and beyond, soas to maintain a certain level of user experience for a given service).The QoS profile can be derived from multiple sources, including forexample the roaming subscriber's “home” MNO, the MVNO/MSO, a subscriberprofile maintained by the MSO or MNO (e.g., high/low value user orsubscription tier), application type/traffic bearer type, as well asinsights from the DPI-based traffic analysis performed by theDPI/analytics engine(s), and can include for example both uplink (UL)and downlink (DL) throughput, allowable PER (packet error rate), jitterspecifications, handover restrictions, idle mode exit policies (e.g.,when the UE is dormant), and latency requirements.

FIG. 4a -5 is a block diagram illustrating one embodiment of an MSO/MNOCBRS network Architecture configured for MNO subscriber roaming to theMSO network. As shown, the network architecture 430 includes the MNOcore interfaces 427-1, 427-n (which may include for example interfacesfrom MNO core to the CBRS core such as eNodeB backhauls, SAS, backoffice provisioning data interfaces, billing and other OSS systems(BOSS)), which interface the respective MNO core(s) 411 with the MSO“back end” 300, 406 (e.g., the HFC and backbone portions of the MSO'splant). As shown (see also FIG. 4a ), this MSO back end is also incommunication with the service domains, specifically the CBSDs 314 viae.g., a DOCSIS or other service “drop” at the service location(s). Datais communicated from the CBSDs 314 in the MSO CBRS RAN to an MSO/MNVOprivate management network.

Within the MNO cores 411 are typical MNO 3GPP/LTE cellular core,entities/processes, including one or more VPN aggregators (foraggregating user data), serving gateways (SGWs), mobility manager entity(MME), MNO AAA server(s), packet/PDN gateways (PGWs), home subscriberservers (HSSs).

Within the MSO/MVNO network 431 of the MSO is a corresponding MME 433,policy server(s) 455, an eDPG (evolved data packet gateway, forinternetworking between the 3GPP EPC (evolved packet core) and untrustedthird party non-3GPP networks), Network Management System (NMS—forconfiguring network settings, collection of statistics, etc.), andElement Management System (EMS—for network element management and datacollection). The operation of the policy server(s) is described ingreater detail below with respect to FIGS. 5-5 c.

Referring now to FIG. 4b , a second embodiment of a network architecture430 useful in implementing the CBRS-based wireless RAT access andco-existence methods of the present disclosure. In this embodiment, adistributed architecture for the MSO controller 310 is utilized, and thedomain proxy 208 is maintained by the MSO as part of the MSO connectionmanager “client” disposed at the venue or area of interest (“servicedomain”). Moreover, the DPI 413 and the MSO CBRS controller 310 arecombined into a common device/function 310 within the MSO networkdomain.

In one implementation, the client devices 306 c may each include aconnection manager (CM) application computer program 474 operative torun on the client and, inter alia, enable the host client device tooperate in a multi-RAT environment (e.g., WLAN, CBRS-LTE, and non-CBRSLTE). As an aside, downloadable application or “app” may be available toclient devices of subscribers of an MSO or cable network (and/or thegeneral public, including MSO “partner” MNO subscribers), where the appallows users to connect to or obtain MSO-provided services whileroaming. Application program interfaces (APIs) may be included in anMSO-provided applications, installed with other proprietary softwarethat comes prepackaged with the client device, or natively available onthe CC or other controller apparatus. Such APIs may include commonnetwork protocols or programming languages configured to enablecommunication with other network entities as well as receipt andtransmit signals that may be interpreted by a receiving device (e.g.,client device). Alternatively, the relevant MNO may provide itssubscribers with the aforementioned functionality (e.g., as a pre-loadedapp on the UE at distribution, or later via download), or as a firmwareupdate to the UE stack conducted OTA.

It will also be appreciated that the connection manager entity (whetheras an individual component, or distributed across two or more platforms,such as via client and server portions disposed respectively) can beconfigured in one implementation to obtain data relating to one or moreperformance or desirability metrics associated with the availablecommunication options, and conduct an evaluation based thereon, Forexample, a quality of service (QoS) related parameter such as BER/PER,and/or strength of signal (e.g., RSSI, RSRP. RSRQ) of each of (i) theMSO-provided CBRS service, and (ii) the MNO-provided cellular service,can be obtained. In one variant, the connection manager app running on aUE can utilize the LTE-based air interface to obtain signal measurementsat the then-present location of the UE, so as to evaluate putativequality of each connection. The UE can, at the direction of theconnection manager, cause autonomous selection of one air interface/RANover the other based on the comparison. When the user selects the appfunction for e.g., automated selection, the UE will, in one variant,detect the availability of the CBRS RAN and LTE (cellular) RAN viasignal strength measurements exceeding a prescribed minimum threshold,and implement selection of one or the other based on evaluation metrics.For instance, such metrics may be as simple as which has the higherrelative (or even absolute, if relatable) signal strength at thatlocation, or alternatively more complex (such as for example being basedon other considerations such as available data bandwidth as signaled bythe corresponding CBRS CBSD or eNB). In another implementation, theconnection manager entity is disposed on an MSO network controllerentity (i.e., a CBRS system controller, or even one or more CBSDs oreNBs), and configured to evaluate the CBRS and MNO cellular options atone or more locations within a prescribed CBRS coverage area (e.g., viause of the one or more CBSD base stations or eNBs). For example, in onevariant, each of the MSO-operated CBSDs includes an RF front end tunableto the relevant frequency bands of interest (i.e., 3.5 GHz as well asprevailing cellular LTE bands in that broader geographic region), suchas via a software-defined radio (SDR), so as to assess the signalcharacteristics at each respective location. The CBRS controller (e.g.,310/310 a/310 b of FIGS. 4 and 4 b) can then generate a data structure(e.g., logic table or “heat map”) indicating the relative quality,strength, or desirability of each frequency band (e.g., LTE cellular RANversus CBRS RAN) at each location, and instruct the relevant UE(s) toutilize their client manager app to invoke selection of one RAN or otherbased thereon.

Methods—

Various methods and embodiments thereof for providing quasi-licensed(e.g., CBRS) spectrum access to roaming MNO subscribers according to thepresent disclosure are now described with respect to FIGS. 5-6.

FIG. 5 illustrates an exemplary embodiment of a method 500 implementedby the system architecture (e.g., the system 400 as discussed above withrespect to FIG. 4a ) to enable connectivity to a quasi-licensed wirelessnetwork (e.g., CBRS network) by a client device such as an LTE-enabledUE of a roaming MNO subscriber. The wireless network useful with method500 is not limited to those embodied in FIGS. 3-4 b herein, and may beused with any wireless-enabled client device and any architectureutilizing data communication among nodes (including those with multiplecoexisting networks).

At step 502, the UE monitors the relevant portion of the quasi-licensedspectrum (e.g., the 3.500-3.770 GHz band) to perform energy detection insupport of CBRS network entry. As discussed elsewhere herein, the UE maybe configured to perform such scans indigenously by its home cellularnetwork (e.g., EUTRAN), or via an app or other software firmwareresident on the UE and supported by the MSO RAN/core. In the exemplaryembodiment, the goal of network entry is to identify and synchronize oneor more CBSDs 314 within the MSO network coverage area, and establish acommunication session therewith. Accordingly, in the exemplaryembodiments, indigenous LTE-TDD capability is used, since suchcapability can be readily utilized within a LTE-enabled UE. Forinstance, certain U.S. MNO LTE networks operating within the 2.5 GHzband utilize TDD, and the CBRS “LTE” networks operating within the 3.5GHz CBRS band of the present disclosure are configured for only TDDoperation. Hence, any LTE operator using the 3.5 GHz band per CBRSAlliance specifications will be an (LTE) TDD operator.

Moreover, use of TDD provides certain benefits with respect tounlicensed operation among multiple users (and hence by extensionquasi-licensed operation such as within CBRS RANs).

Per step 504, the UE evaluates the monitoring data of the prescribedquasi-licensed spectrum to determine an energy level or establish“detection” of a CBSD of sufficient strength/proximity (e.g., based onRSSI or other value exceeding a prescribed threshold). This willdetermine if the UE is within the MSO coverage area; other techniquesfor detection of coverage may be used as well, consistent with thepresent disclosure. If the UE is not within coverage (e.g., no MSO CBSDsdetected), monitoring continues according to a prescribed schedule ofhigher-layer logic.

Alternatively, if the CBSD 314 is detected, the UE attempts tosynchronize with the CBSD (step 506) according to the prescribedprotocol (e.g., establishing timing via hypothesis testing, readingbroadcast channels such as PDCCH and decoding preambles and other data,per step 508) so as to enable the UE to at least transact itsUE-specific data (e.g., IMSI) with the CBSD per step 510. The data isthen passed to the MSO controller 310 (and core 412), and the UE data isaccessed from the MNO (or if resident in the MSO database 404 or privatenetwork 431) so that the UE is authenticated to the MSO RAN and core(step 512). Once authenticated, it is provisioned within the CBRS RAN(e.g., as to TDD parameters such as slots, time-frequency resources,CBRS sub-bands, etc.) per step 514, and connected to its “home” MNO core411 via the MSO core 412 and LTE interfaces 427 per step 516. Asdescribed in greater detail below, such connection may also includeimposition or enforcement of one or more policies for the user datatransacted by the UE, such as QoS requirements, prioritization based onMNO identity and/or type of traffic (e.g., voice, data, etc.).

Referring now to FIG. 5a , one exemplary embodiment of an MSO CBRSsystem bandwidth management methodology is now described in detail.

As shown in FIG. 5a , the method 550 includes first configuring new QoSprofiles for MNO roaming user devices (UEs) within the MSO CBRS RAN EMS433 (e.g., located in the MSO/MNO AAA architecture) per step 552.

The MSO CBRS RAN controller SGW 434 then retrieves the QoS profile andthe associated service class ID values (e.g., from one or moredesignated entities within the MSO and/or MNO cores) per step 554. Forexample, in one implementation, the QoS profiles are stored concurrentlywithin the MSO subscriber and CBRS database 404 (FIG. 4a ), such aswhere the MNO provides a list of its subscribers (and associated data)to the “partner” MSO such that the MSO can maintain that data for rapidaccess within the MSO network core or infrastructure (e.g., the partnerMNO subscribers are “pseudo-subscribers” of the MSO, and maintainedwithin the MSO subscriber database as such). In another implementation,the MNO maintains QoS profiles for its roaming subscribers, which aremade accessible to the MSO CBRS controller logic when the subscribersroam and request CBRS service (or otherwise “enter” the CBRS coveragearea and are recognized by the CBSD(s) and CBRS controller). Myriadother approaches will be recognized by those of ordinary skill given thepresent disclosure, the foregoing being merely exemplary.

Next, the BSS/OSS 454 updates the MNO user's device profile with theappropriate service plan per step 556. Depending on the location of theprofile data (e.g., whether within MSO network, MNO network, or even UEitself), appropriate protocols and communications modalities areutilized to perform the update. In one implementation, the update isperformed within the MSO's CBRS RAN, the MSO core, and backhaul portionsof the MSO network.

Next, the roaming MNO UE performs network entry (such as via theprocedure of FIGS. 5 and 6) into the MSO CBRS RAN per step 558. The CBRSRAN controller SGW 434 then authenticates the UE (see FIG. 5a ), andretrieves the service class ID for the UE per step 560.

The SGW 434 then provides the relevant QoS parameters (based on theservice class ID) to the relevant CBSD(s) 314 of the CBRS RAN per step562.

The CBSD 314 (under direction of the controller 310) then performsbandwidth management and UE scheduling per the relevant QoS profile perstep 564.

Referring now to FIG. 5c , one embodiment of a provisioning methodologyaccording to the disclosure is described. As shown, the method 570 firstcreates one or more roaming MNO user policies within the policyserver/enforcer 455 of the MSO network per step 572 (see FIG. 4a -5). Aspreviously described, the user policies may be associated with aparticular MNO roaming user device (e.g., a given UE, based onparticular identifying data thereof), and stored within e.g., the MSOinfrastructure (e.g., with a subscriber/pseudo-subscriber database).

Next, per step 574, the policy server/enforcer system 455 provides datadescriptive of the policies to the DPI server 413, so as to enable theDPI processes to perform DPI on the user data flows to enforce thepolicies (step 576). For example, in one implementation, the policyserver(s) 455 provide data indicative of a QoS policy to be applied toone or more MNO roaming users when within the MSO CBRS RAN, based ontype of user data application (e.g., data, video, voice, etc.) and otherattributes associated with the particular MNO roaming user and UE, aswell as other attributes of the bearer(s) used to support the requestedservices.

FIG. 6 is a ladder diagram illustrating an exemplary communications flow600 for configuring and controlling CBRS connectivity for one or moreroaming MNO users within an area or venue.

At step 602 of the exemplary embodiment, a CBSD 314 sends aninterference report to the designated DP 208. Data of these reports areforwarded to the cognizant FSAS(s) 202 by the DP 208 according to theproper FSAS protocol. The reports may contain information related to,e.g., transmit power of nearby access points and nodes, number of users,channels used, data transmission rates, beamforming settings,modulation/coding scheme (MCS), or other statistics associated withsignals propagating within the venue, e.g., signals related to CBRSsub-bands in the 3.550-3.700 GHz range. Per step 604, the MSO controller310 (here, with integrated DPI/analytics engine 413) decides it needsCBRS spectrum allocated (for whatever reason; e.g., in response to anynumber of scenarios such as those of FIGS. 5-5 c discussed above), andinvokes a communication protocol with the DP 208. Such protocol mayinclude for example an authentication (e.g., challenge-response) of theMSO controller 310 by the DP, and conversely authentication of the DP208 by the MSO controller 310 or its security proxy, so as to e.g.,mitigate spoofing or MI™ attacks.

Once the DP/controller are mutually authenticated, the DP 208 generatesa spectrum request message on behalf of the controller 310 fortransmission to the FSAS 202 per step 606. Per step 608, the FSAS 202responds to the DP 208 with a spectrum grant (or rejection), which isthen symmetrically sent to the MSO controller 310 per step 610 using theappropriate MSO/DP protocols (which may differ from those of the FSAS).

Per step 611, the MSO controller 310, after evaluating and conductingoptimization of spectrum sub-band allocations to the various CBSDswithin a given venue/area (and optionally other venues/areas, dependingon coverage), issues its optimized allocations of the sub-bands to theCBSDs 314 of the one or more areas/venues. At this point, the CBSDsconfigure for operation in the allocated sub-bands (e.g., LTE band 43),and broadcast on their DL channels to advertise their availability toany client/UE within range of the CBSD(s).

Specifically, as is known, LTE systems utilize OFDM on their DL (base toUE), and SC-FDMA on their UL (UE to base), and further employ a numberof shared/control channels for a variety of control, signaling, andother functions. These channels exist in both DL and UL directions, andinclude the: (i) physical downlink control channel (PDCCH); (ii)physical uplink control channel (PUCCH); (iii) physical downlink sharedchannel (PDSCH); and (iv) physical uplink shared channel (PUSCH). Thesechannels can be decoded by the UE and used to establish communicationwith the CBSD 314.

Also, per steps 612 and 613, the MSO controller 310 will generate anoptimized policy input to the CBRS core (and ultimately the relevantMNO), and the CBRS RAN (i.e., CBSD) based on the policy considerationsincluding MNO user/network policies applicable to the roaming MNOsubscriber, such as for bulk billing and provisioning operations,whether by the MSO or MNO.

In the exemplary embodiment, optimization functions within the MSOcontroller 310 takes into consideration network state, topology, load,and user requirements, and generate a standardized request to the SASservice based thereon. The optimization functions also “tune” theresponse from the SAS entity before sending it to the CBSD 314 and MNOCore 412 (see FIGS. 4a and 6). Mobility optimization takes SAS changes,SON functions, and policies, as well as priorities of different traffictypes (voice/video/data, etc.) to/from MNO cores. Moreover, prioritiesof a given MNO and its users for the CBRS operator (e.g., MSO), as wellas the DPI analytics data generated by the DPI/analytics engine 413, aretaken into account by the optimization functions of the controller aswell, as described in greater detail supra.

In operation, the LTE UE will report its CSI (channel state information,including CQI or channel quality index) via one of the UL channels;i.e., PUSCH or PUCCH, thereby characterizing the RF receivingenvironment for each reporting UE. The eNodeB takes the reported CSIinformation to develop a schedule for transmission to the UE(s) via thePDSCH, and DL resource allocation is made via the PDCCH. UL grants (forUE traffic operations such as when no PUSCH is available) are also madeby the eNodeB via the PDCCH, based on requests sent via the PUCCH.

Hence, per step 614, the UE(s) receive the broadcast channels,synchronize and determine timing (e.g., via CAZAC sequence analysis),and then establish UL communication with the CBSD (operating effectivelyas an eNodeB) within the sub-bands of interest, including authenticationand sign-on of the UE to the MNO network. The latter is facilitated inone implementation via one or more service establishment requests to theMNO's designated EUTRAN entity per step 616; e.g., to validate the UE'smobile ID and other subscription information, and enabling transactionof UP (user plane) data between the client device and the eNodeB. Inthis implementation, the MSO infrastructure acts effectively as aconduit or extension of the MNO network, with the MNO core 411 conducingall of the relevant communications operations to establish the UE/eNBsession per the LTE standards, with the CBSD(s) 314 acting as its proxywithin the MSO network.

Per step 617, MSO core-to-MNO core user data connectivity is establishedsuch that the CBRS-serviced call data (e.g., user data such as voicedata or video data) can be transacted between the MSO core and MNO coreusing a high-capacity backhaul (e.g., for at least a portion of the MSOnetwork, a DOCSIS 3.0 or 3.1 backhaul from the CBSD(s) 314 is used, andthe data forwarded via the MSO core (e.g., backbone thereof) to the MNOnetwork using for example extant network transport protocols such asTCP/UDP.

Per step 618, the CBSD, the session is optionally configured accordingto one or more MSO policies as dictated by the controller 310 (andindirectly by the partner MNOs); i.e., according to e.g., previouslyagreed-upon policies between the MSO and MNO 411, and these policies forthe particular session are then communicated to the MNO. See discussionof FIGS. 5-5 c presented elsewhere herein.

CBRS Controller Apparatus—

FIG. 7 illustrates a block diagram of exemplary hardware andarchitecture of a controller apparatus, e.g., the CBRS controller 310 ofFIG. 4a , useful for operation in accordance with the presentdisclosure.

In one exemplary embodiment as shown, the controller 310 includes, interalia, a processor apparatus or subsystem 702, a program memory module704, a connectivity manager module 706 a (here implemented as softwareor firmware operative to execute on the processor 702), a back-end(inward-facing) network interface 710 for internal MSO communicationsand control data communication with the relevant CBSD(s) 314 and the DPIServer 413, and a front-end or outward-facing network interface 708 forcommunication with the DP 208 (and ultimately the FSAS 202 via a Federalsecure interface network, or CSAS 420) via an MSO-maintained firewall orother security architecture. Since CBRS controllers could feasibly beemployed for surreptitious activity, each should be secure from, interalia, intrusive attacks or other such events originating from the publicInternet/ISP network 311 (FIG. 3a ) or other sources.

Accordingly, in one exemplary embodiment, the controllers 310 are eachconfigured to utilize a non-public IP address within a CBRS “DMZ” of theMSO network. As a brief aside, so-called DMZs (demilitarized zones)within a network are physical or logical sub-networks that separate aninternal LAN, WAN, PAN, or other such network from other untrustednetworks, usually the Internet. External-facing servers, resources andservices are disposed within the DMZ so they are accessible from theInternet (and hence e.g., DPs 208 responding to MSO-initiated CBRSspectrum allocation requests), but the rest of the internal MSOinfrastructure remains unreachable or partitioned. This provides anadditional layer of security to the internal infrastructure, as itrestricts the ability of surreptitious entities or processes to directlyaccess internal MSO servers and data via the untrusted network, such asvia a DP “spoof” or MI™ attack.

In addition, the controller 310 of the exemplary implementation isconfigured to only respond to a restricted set of protocol functions;i.e., authentication challenges from a valid DP 208 or SAS 202 (i.e.,those on a “white list” maintained by the MSO), requests forinterference monitoring data from a DP or SAS, resource allocation ACKs,etc.

Although the exemplary controller 310 may be used as described withinthe present disclosure, those of ordinary skill in the related arts willreadily appreciate, given the present disclosure, that the controllerapparatus may be virtualized and/or distributed within other network orservice domain entities (as in the distributed controller architectureof FIG. 4b ), and hence the foregoing apparatus 310 is purelyillustrative.

More particularly, the exemplary controller apparatus 310 can bephysically located near or within the centralized operator network(e.g., MSO network); within or co-located with a CBSD (as in theembodiment of FIG. 4b ); within an intermediate entity, e.g., within adata center, such as a WLAN AP controller (see FIG. 4c ); and/or within“cloud” entities or other portions of the infrastructure of which therest of the wireless network (as discussed supra) is a part, whetherowned/operated by the MSO or otherwise. In some embodiments, the CBRScontroller 310 may be one of several controllers, each having equivalenteffectiveness or different levels of use, e.g., within a hierarchy(e.g., the controller 310 may be under a “parent” controller thatmanages multiple slave or subordinate controllers, with each of the“slaves” for example being designated to control functions within theirown respective venue(s)).

In one embodiment, the processor apparatus 702 may include one or moreof a digital signal processor, microprocessor, field-programmable gatearray, or plurality of processing components mounted on one or moresubstrates. The processor apparatus 702 may also comprise an internalcache memory. The processing subsystem is in communication with aprogram memory module or subsystem 704, where the latter may includememory which may comprise, e.g., SRAM, flash and/or SDRAM components.The memory module 704 may implement one or more of direct memory access(DMA) type hardware, so as to facilitate data accesses as is well knownin the art. The memory module of the exemplary embodiment contains oneor more computer-executable instructions that are executable by theprocessor apparatus 702. A mass storage device (e.g., HDD or SSD, oreven NAND flash or the like) is also provided as shown.

The processor apparatus 702 is configured to execute at least onecomputer program stored in memory 704 (e.g., the logic of the CBRScontroller in the form of software or firmware that implements thevarious controller functions described herein with respect to CBRSspectrum allocation, CBSD environmental monitoring, etc.). Otherembodiments may implement such functionality within dedicated hardware,logic, and/or specialized co-processors (not shown).

In one embodiment, the mobility optimization manager 706 a is furtherconfigured to register known downstream devices (e.g., access nodesincluding CBSDs and WLAN APs), other backend devices, and wirelessclient devices (remotely located or otherwise), and centrally controlthe broader wireless network (and any constituent peer-to-peersub-networks). Such configuration include, e.g., providing networkidentification (e.g., to CBSDs, APs, client devices such as roaming MNOUEs, and other devices, or to upstream devices), identifying networkcongestion, Self Optimization (SO) functions, and managing capabilitiessupported by the wireless network.

Moreover, as described previously herein, MSO and MNO network and userpolicies may implemented using the controller logic 706 a. In oneimplementation, one or more primary factors is/are used as a basis tostructure the optimization to maximize or optimize the primaryfactor(s). For example, if the goal at given instance is to push alarger amount of data (i.e., throughput) such as in the downlinkdirection (DL), the UEs or devices with better signaling may be chosenby the optimization logic to transact more data in an efficient manner(effectively “path of least resistance” logic). This can also be appliedto for instance a higher subscriber service tier vs. a lower subscribertier; the higher tier may be allocated available bandwidth (at least toa prescribed degree or value) before bandwidth is allocated to the lowertier, so as to ensure the user experience for the higher tier issufficient. Alternatively, the goal may be more equitable distributionof resources (i.e., radio/backhaul/core resources) among differentusers, access networks, partners and/or different types of services(e.g., voice versus data, QoS versus non-QoS, etc.), logic to balancethe resources across the different user, etc. may be employed. See,e.g., U.S. Pat. No. 9,730,143 to Gormley, et al. issued Aug. 8, 2017 andentitled “Method and apparatus for self organizing networks;” U.S. Pat.No. 9,591,491 to Tapia issued Mar. 7, 2017 entitled “Self-organizingwireless backhaul among cellular access points;” and U.S. Pat. No.9,730,135 to Rahman issued Aug. 8, 2017, entitled “Radio access networkresource configuration for groups of mobile devices,” each of theforegoing incorporated herein by reference in its entirety, forexemplary SON implementations useful with various aspects of the presentdisclosure.

In the exemplary embodiment, optimization functions within the MSOcontroller 310 takes into consideration network state, topology, load,and user requirements, and generate a standardized request to the SASservice based thereon. The optimization functions also “tune” theresponse from the SAS entity before sending it to the CBSD 314 and MNOCore 412 (see FIGS. 4a and 6). Mobility optimization takes SAS changes,SON functions, and policies, as well as priorities of different traffictypes (voice/video/data, etc.) to/from MNO cores. Moreover, prioritiesof a given MNO and its users for the CBRS operator (e.g., MSO), as wellas the DPI analytics data generated by the DPI/analytics engine 413, aretaken into account by the optimization functions of the controller aswell, as previously described herein.

In one embodiment, the mobility optimization manager 706 a accesses themass storage 705 (or the CBRS DB 404) to retrieve stored data. The dataor information may relate to reports or configuration files as notedabove. Such reports or files may be accessible by the mobilityoptimization manager 706 a and/or processor 702, as well as othernetwork entities, e.g., a CM 444 provisioning server 417 (FIG. 4b ) orwireless nodes (CBSDs 314 a or APs 314 b).

In other embodiments, application program interfaces (APIs) such asthose included in an MSO-provided applications, installed with otherproprietary software, or natively available on the controller apparatus(e.g., as part of the computer program noted supra or exclusivelyinternal to the mobility optimization manager 706 a) may also reside inthe internal cache or other memory 704. Such APIs may include commonnetwork protocols or programming languages configured to enablecommunication with other network entities as well as receipt andtransmit signals that a receiving device (e.g., CBSD, WLAN AP, clientdevice) may interpret.

The mobility optimization manager 706 may further be configured todirectly or indirectly communicate with one or more authentication,authorization, and accounting (AAA) servers 450 of the network (see FIG.4a -4). The AAA servers are configured to provide services for, e.g.,authorization and/or control of network subscribers (including roamingMNO “visitors”) for controlling access and enforcing policies relatedthereto with respect to computer resources, enforcing policies, auditingusage, and providing the information necessary to bill for services.

In some variants, authentication processes are configured to identify aCBSD 314 or an AP 314 b, a client device 306 c, or an end user, such asby having the client device identify or end user enter valid credentials(e.g., user name and password, or Globally Unique Identifier (GUID))before network access or other services provided by the operator may begranted to the client device and its user (see discussion of FIGS. 5-5 cand 6 above). Following authentication, the AAA servers may grantauthorization to a roaming MNO subscriber for certain MSO-providedfeatures, functions, and/or tasks, including access to MSO-providedcloud storage, streaming content, billing information, exclusive mediacontent, etc. Authentication processes may be configured to identify orestimate which of the known CBSDs 314 a serviced by the CBRS controller310 tend to serve roaming MNO subscribers, thereby providing additionalinsights with respect to how a particular CBSD may be treated. Forexample, if a first CBSD serves many MNO subscribers relative to anotherCBSD or AP, the controller 310 may favor the first CBSD by, e.g.,allocating CBRS sub-bands preferentially or in greater number/bandwidthor other “preferences”, resulting in a better or additional end-userexperiences for the users (ostensibly many roaming MNO subscribers)using that first CBSD.

Returning to the exemplary embodiment as shown in FIG. 7, one or morenetwork “front-end” or outward-facing interfaces 708 are utilized in theillustrated embodiment for communication with external (non-MSO) networkentities, e.g., DPs 208, via, e.g., Ethernet or other wired and/orwireless data network protocols.

In the exemplary embodiment, one or more backend interfaces 710 areconfigured to transact one or more network address packets with otherMSO networked devices, particularly backend apparatus such as theMSO-operated CBSDs 314 a and WLAN APs 314 b (FIG. 7b ) within the targetvenue/area. Other MSO entities such as the MSO CMTS, Layer 3 switch,network monitoring center, AAA server, etc. may also be in communicationwith the controller 310 according to a network protocol. Common examplesof network routing protocols include for example: Internet Protocol(IP), Internetwork Packet Exchange (IPX), and Open SystemsInterconnection (OSI) based network technologies (e.g., AsynchronousTransfer Mode (ATM), Synchronous Optical Networking (SONET), SynchronousDigital Hierarchy (SDH), Frame Relay). In one embodiment, the backendnetwork interface(s) 710 operate(s) in signal communication with thebackbone of the content delivery network (CDN), such as that of FIGS.3-4 c. These interfaces might comprise, for instance, GbE (GigabitEthernet) or other interfaces of suitable bandwidth capability.

It will also be appreciated that the two interfaces 708, 710 may beaggregated together and/or shared with other extant data interfaces,such as in cases where a controller function is virtualized withinanother component, such as an MSO network server performing thatfunction.

It will be recognized that while certain aspects of the disclosure aredescribed in terms of a specific sequence of steps of a method, thesedescriptions are only illustrative of the broader methods of thedisclosure, and may be modified as required by the particularapplication. Certain steps may be rendered unnecessary or optional undercertain circumstances. Additionally, certain steps or functionality maybe added to the disclosed embodiments, or the order of performance oftwo or more steps permuted. All such variations are considered to beencompassed within the disclosure disclosed and claimed herein.

While the above detailed description has shown, described, and pointedout novel features of the disclosure as applied to various embodiments,it will be understood that various omissions, substitutions, and changesin the form and details of the device or process illustrated may be madeby those skilled in the art without departing from the disclosure. Thisdescription is in no way meant to be limiting, but rather should betaken as illustrative of the general principles of the disclosure. Thescope of the disclosure should be determined with reference to theclaims.

It will be further appreciated that while certain steps and aspects ofthe various methods and apparatus described herein may be performed by ahuman being, the disclosed aspects and individual methods and apparatusare generally computerized/computer-implemented. Computerized apparatusand methods are necessary to fully implement these aspects for anynumber of reasons including, without limitation, commercial viability,practicality, and even feasibility (i.e., certain steps/processes simplycannot be performed by a human being in any viable fashion).

What is claimed is:
 1. A computerized method for providing wirelessservice within a first wireless network infrastructure to a computerizedmobile user device served by a second wireless network infrastructure,the computerized method comprising: at least temporarily registering thecomputerized mobile user device with the first wireless networkinfrastructure; selecting at least one quasi-licensed band for use bythe computerized mobile user device within the first wireless networkinfrastructure; communicating data to the computerized mobile userdevice enabling the computerized mobile user device to access theselected at least one quasi-licensed band for use; establishingcommunication with the computerized mobile user device using the atleast one quasi-licensed band via one or more access points of the firstwireless network infrastructure; and communicating user data to and fromthe computerized mobile user device via a data interface between thefirst wireless network infrastructure and the second wireless networkinfrastructure, wherein the communicating of the user data is conductedaccording to at least one user-specific policy associated with thecomputerized mobile user device, the at least one user-specific policyspecified by the second wireless network infrastructure and based onparticular information identifying the computerized mobile user device.2. The computerized method of claim 1, wherein the communicating datacomprises transmitting the data to the computerized mobile user devicevia the data interface between the first wireless network infrastructureand the second wireless network infrastructure.
 3. The computerizedmethod of claim 1, wherein the user data is generated as part of acommunication session established using the at least one quasi-licensedband and the one or more access points.
 4. The computerized method ofclaim 1, wherein the first wireless network infrastructure comprises amanaged cable or satellite service provider network, and the secondwireless network infrastructure comprises a cellular network.
 5. Thecomputerized method of claim 1, wherein the establishing communicationwith the computerized mobile user device using the at least onequasi-licensed band via the one or more access points of the firstwireless network infrastructure comprises using a Long TermEvolution-Time Division Duplex (LTE-TDD) protocol to establishcommunication within a Citizens Broadband Radio Service (CBRS)quasi-licensed band via at least one Citizens Broadband Radio ServiceDevice (CBSD).
 6. The computerized method of claim 1, wherein theestablishing the communication with the computerized mobile user deviceusing the at least one quasi-licensed band via the one or more accesspoints of the first wireless network infrastructure comprises imposingat least one service policy associated with the second wireless networkinfrastructure as part of the communication.
 7. The computerized methodof claim 6, further comprising generating the user data as part of acommunication session established using the at least one quasi-licensedband and the one or more access points; and wherein the imposing the atleast one service policy associated with the second wireless networkinfrastructure as part of the communication comprises imposing a QoS(quality of service) policy for at least a portion of the user data. 8.The computerized method of claim 1, further comprising generating theuser data as part of a communication session established using the atleast one quasi-licensed band and the one or more access points; andwherein the communicating the user data comprises prioritizing the userdata with respect to other user data transacted by the one or moreaccess points.
 9. The computerized method of claim 1, furthercomprising, prior to the selecting the at least one quasi-licensed bandfor use by the computerized mobile user device within the first wirelessnetwork infrastructure: transmitting data representative of a spectrumrequest to a spectrum allocation authority; and receiving a spectrumgrant from the spectrum allocation authority for at least a period oftime, the spectrum grant including the at least one quasi-licensed band.10. The computerized method of claim 1, wherein the at least temporarilyregistering the computerized mobile user device with the first wirelessnetwork infrastructure comprises obtaining data specific to thecomputerized mobile user device from an authentication entity of thesecond wireless network infrastructure.
 11. A computerized method forproviding mobile visiting access services for at least one computerizedmobile client device, the at least one computerized mobile client deviceconfigured to use first and second wireless protocols, the computerizedmethod comprising: registering, while the at least one computerizedmobile client device is utilizing the first wireless protocol, the atleast one computerized mobile client device with a temporary serviceprovider network, the temporary service provider network comprising botha radio access network (RAN) and a core portion; allocatingquasi-licensed spectrum to the at least one computerized mobile clientdevice for use within the RAN; and causing the at least one computerizedmobile client device to transition from the first wireless protocol tothe second wireless protocol.
 12. The computerized method of claim 11,wherein the first wireless protocol comprises a Long Term Evolution(LTE)-FDD (frequency division duplex) cellular protocol, and the secondprotocol comprises an LTE-TDD (time division duplex) protocol.
 13. Thecomputerized method of claim 11, wherein the allocating quasi-licensedspectrum comprises: transmitting data to a domain proxy (DP), the DPconfigured to communicate at least a portion of the data to a SpectrumAccess System (SAS) to obtain access to a Citizens Broadband RadioService (CBRS) band; receiving from the DP data indicating a CBRS bandallocation; and allocating at least a portion of the CBRS bandallocation for use by at least one computerized mobile client device incommunicating with an access point of the RAN.
 14. The computerizedmethod of claim 11, wherein the registering the at least onecomputerized mobile client device with a temporary service providernetwork comprises: receiving, from a cellular service provider networkcore portion, data indicative of the at least one computerized mobiledevice; and utilizing the received data to authenticate the at least onecomputerized mobile device within the temporary service provider networkpursuant to a service request issued from the at least one computerizedmobile client device.
 15. The computerized method of claim 14, furthercomprising: establishing data communication between the at least onecomputerized mobile user device and the cellular service providernetwork; and transacting one or more messages between a computerizeduser device of the cellular service provider network and the at leastone computerized mobile user device via the cellular service providernetwork and the temporary service provider network.
 16. The computerizedmethod of claim 15, wherein the transacting the one or more messagesbetween the computerized user device of the cellular service providernetwork and the at least one computerized mobile user device via thecellular service provider network and the temporary service providernetwork comprises utilizing both a core portion of the cellular serviceprovider network and a core portion of the temporary service providernetwork.
 17. The computerized method of claim 11, wherein theregistering the at least one computerized mobile client device with thetemporary service provider network comprises: receiving, at thetemporary service provider network, a service request issued from the atleast one computerized mobile client device, the service requestcomprising data identifying the at least one computerized mobile clientdevice; transmitting the comprising data identifying the at least onecomputerized mobile client device to an authentication entity of acellular service provider; and receiving data authenticating the atleast one computerized mobile client device.
 18. Computerized networkapparatus for use within a first network and configured to at leasttemporarily provide wireless service within a quasi-licensed frequencyband to subscribers of a second network, the computerized networkapparatus comprising: digital processor apparatus; network interfaceapparatus in data communication with the digital processor apparatus andconfigured to transact data with one or more computerized entities ofthe second network; and a storage apparatus in data communication withthe digital processor apparatus and comprising at least one computerprogram, the at least one computer program configured to, when executedon the digital processor apparatus: receive first data from the one ormore computerized entities, the first data relating to a computerizedsubscriber device operative within the second network; receive seconddata pursuant to a request for wireless service from the computerizedsubscriber device; based at least on the received first and second data,authenticate the computerized subscriber device; allocate quasi-licensedspectrum for use by at least the computerized subscriber device; andcause transmission of first data to the one or more computerizedentities of the second network, the first data enabling the computerizedsubscriber device to utilize the allocated quasi-licensed spectrum. 19.The computerized network apparatus of claim 18, wherein the at least onecomputer program is further configured to, when executed on the digitalprocessor apparatus, enable transaction of user data over at least acore portion of the first network and a core portion of the secondnetwork and via a data interface between the first and second networks.20. The computerized network apparatus of claim 19, wherein thetransaction of the user data over at least a core portion of the firstand second networks is configured to be conducted according to at leastone user-specific or device-specific policy specified by the secondnetwork.